Many internal companies use Newsletter services such as Mailchimp to email out internal newsletters. The From Address of this is usually an internal email address which means it will get rejected by the anti spoofing policy

Option 1

In Mimecast Administration Panel go to : 

Administration -> Gateway -> Policies -> Anti Spoofing SPF based Bypass

  1. Add the following Policy, this will only whitelist IP’s in your SPF Record,  so putting servers.mcsv.net will not work , you will also have to put “ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16” in your SPF record. If your SPF is over 255 characters : try option 2

 

Option 2

Administration -> Gateway -> Policies -> Anti Spoofing

Add the policy below , you can get a list of IP’s Mailchimp user here

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

If you are trying to get the size of your Synology Volume via SNMP < you will need to query the correct Index on the OID .1.3.6.1.2.1.25.2.3.1.3.

Synology does not have standard indexes , so you will need to start by downloading run and install SNMP walk on a machine that can communicate to the device over network

Enter the IP of the device in SNMP Walk ( Leave rest options to default ) and get the output to text File

Open the txt file and do a Search for volume and per below you should fine the list of OID’s

The last number will be the index , for example Index will be 41 fo the volume

.1.3.6.1.2.1.25.2.3.1.3.1 = STRING: “Physical memory”
.1.3.6.1.2.1.25.2.3.1.3.3 = STRING: “Virtual memory”
.1.3.6.1.2.1.25.2.3.1.3.6 = STRING: “Memory buffers”
.1.3.6.1.2.1.25.2.3.1.3.7 = STRING: “Cached memory”
.1.3.6.1.2.1.25.2.3.1.3.8 = STRING: “Shared memory”
.1.3.6.1.2.1.25.2.3.1.3.10 = STRING: “Swap space”
.1.3.6.1.2.1.25.2.3.1.3.31 = STRING: “/”
.1.3.6.1.2.1.25.2.3.1.3.36 = STRING: “/tmp”
.1.3.6.1.2.1.25.2.3.1.3.37 = STRING: “/run”
.1.3.6.1.2.1.25.2.3.1.3.38 = STRING: “/dev/shm”
.1.3.6.1.2.1.25.2.3.1.3.41 = STRING: “/volume1”

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently , users where getting the below error from a Web App they use

This is due to the mixed code security which needs to be set to : “Enable – hide warning and run with protections”

To deploy this setting to all computers on a network via Group Policy follow the guide below , here is the Java Reference

Create a GP to delpoy the following file to C:\Windows\Sun\Java\Deployment\deployment.config

deployment.system.config.mandatory=true
deployment.system.config=file:///C:/WINDOWS/Sun/Java/Deployment/deployment.properties

Create a GP to delpoy the following file to C:\Windows\Sun\Java\Deployment\deployment.properties

# Mixed code (sandbox vs. trusted) security verification
deployment.security.mixcode=HIDE_RUN
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had a few Zerto Recovery Groups ( VPG’s ) came up with the state 

Recovery is possible. (0%)

Connecivity to the VM’s where ok , and when I ran through the Wizard after Editing the VPG is came back with all ticks. A reboot of the server and SCVMM server did not clear the issue either

In the end we had to perform a “Force Sync” to resync the delta’s

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I was trying to add a Virtual Switch to a new Hyper V Server and I got an error similar to below

Image result for adding ports to the switch failed hyper v

Although the Virtual Switch seemed to add ok , it was coming up with Errors in the Cluster Manager ( Status Unavailable ) 

The server was actually already added to the Failover Cluster Manager. And I noticed that the

“Microsoft vmm dhcpv4 server switch extension” filter was missing. This gets added to a Node on adding to cluster

Evicting the Hyper V host from the Cluster then deleting and re-adding the VSwitch Resolved this

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I was trying to get a WDS server PXE Booting using Legacy and UEFI booting. I followed the DHCP guide here Legacy worked however UEFI was not working. I double checked on the WDS server for the 67 Option with a file share and in

\\%IPOFSERVER%\reminst\Boot\x64

wdsnbp.com existed but no wdsmgfw.efi

Running a rebuild of the boot files also did not fix this for some reason , in the end I copied the file from : 

\\%IPOFSERVER%\c$\Windows\System32\RemInst\boot\x64

and it resolved the issue

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

So you are fully up-t0-date with Outlook however you are having issues with performance

  1. The first thing Microsoft 365 support will do it recreate your profile, and also recreate your OST , so make sure you have done this
  2. Next they will get you to run this :  Microsoft Support and Recovery Assistant for Office 365 (also known as ‘SaRA’). If will give you a list of problems you can work towards resolving
  3. Make sure you upgrade to 64bit Version of Office

Outlook display issues only affect 32-bit versions of Office. Normally, 32-bit applications can only access 2 GB of memory that all 32-bit apps share. Outlook appears to handle this limit poorly, making it unusable once available memory dips below what Outlook requires to run smoothly.

To see how much memory is available for Outlook, try the VMMap Sysinternals tool, which shows the private bytes or memory distributed for a process that cannot be shared. VMMap shows the bit version of Outlook, as well. For 32-bit Outlook, a number at 250,000 K or less is bad.

Use the following registry setting to prevent add-ins from using the extra memory available from LAA mode. Change the xx to 15 for Outlook 2013 or 16 for Outlook 2016:
HKEY_CURRENT_USER\Software\Microsoft\Office\xx.0\Outlook\ReserveHighAddressRange DWORD Value ‘1’

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

How to get the OneDrive .ADMX files for Group Policies

On a machine with the latest of One Drive for Business installed, navigate to : %localappdata%\Microsoft\OneDrive

Find the latest version number in the folder and open it then go to the adm folder and copy the  .admx file

to \\domain.local\SYSVOL\domain.local\Policies\PolicyDefinitions and .adml file to \\domain.local\SYSVOL\domain.local\Policies\PolicyDefinitions\en-us\

Set Policies

Configure your Group Policies to the settings you want, but the one you’ll need for auto sign in is “Silently configure OneDrive using Windows 10 or domain credentials“. ) This will set : [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive] “SilentAccountConfig”=dword:00000001. 

and also it will set Modern Authentication: 

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\OneDrive] “EnableADAL”=dword:00000001 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)