Get-MailboxFolderStatistics kevin.whyte@token.com.au | Where {$_.ItemsInFolder -eq 0} | Select Identity
Recently I tried to stop a VPG in Zerto after some DR testing, however, the Stop failed and the errors showing where :
Forcibly delete VPG in Error State : Undo Log Isn’t Empty can’t start new transaction
After lodging a call with Zerto Support, we had to forcibly remove the VPG Via Powershell and Re-Add it back
**Before you do this I recommend you log down all the VM’s in the VPG and the Temp Data Drives
You will need to download and install the Zerto Powershell Tools : Zerto.PS.Commands.Installer for your version
After this is run you need to Open the Zerto Powershell and run
ForceRemove-ProtectionGroup
Enter the VPG Name without Quotes
Enter the IP of the Zerto Server and username and password ( admin / password )
Once removed you can use the Zerto Virtual Replication Diagnostic Tool to import the VPG from the old setting file :
Then navigate to :
C:\Program Files\Zerto\Zerto Virtual Replication\ExportedSettings
Find the latest backup and try and re-import the VPG
If this fails for whatever reason you will need to use the GUI at the customer side to recreate manually hence Note to backup VM names and Temp Data Drivers
A customer was using Sharepoint via office 365 using Drive Mappings to their different libraries. We use Network locations deployed via group policy to enable users to access files in Windows Explorer. The customer uses 2fa however we have AD Premium P1 Licenses to whitelist the Office IP’s.
The customer would need to login to Internet explorer once and save the browser cookie and the drives would map.
This was working fine until we enabled AAD connect Single Sign in their environment to simplify signing in. Drives would suddenly start to drop off randomly. Remapping a single library manually by going to any one of the libraries and choosing “View in File Explorer” per below would fix the issue until the next day
Remove the AAD connect Single Sign in from their environment resolved the issue …. must be a bug with SSO and Passing through Sharepoint libraries in IE
Get-Mailbox -RecipientTypeDetails SharedMailbox -ResultSize:Unlimited | Get-MailboxPermission | select identity,user,accessrights | where { ($_.User -like ‘*@*’) }
23.103.132.0/22
23.103.136.0/21
23.103.144.0/20
23.103.198.0/23
23.103.200.0/21
40.92.0.0/14
40.107.0.0/16
52.100.0.0/14
65.55.88.0/24
65.55.169.0/24
94.245.120.64/26
104.47.0.0/17
134.170.101.0/24
134.170.140.0/24
134.170.171.0/24
157.55.133.160/27
157.56.87.192/26
157.56.110.0/23
157.56.112.0/24
157.56.116.0/25
157.56.120.0/25
207.46.51.64/26
207.46.100.0/24
207.46.108.0/25
207.46.163.0/24
213.199.154.0/24
213.199.180.128/26
216.32.180.0/23
Recently trying to release and whitelist an item using Barracuda’s cloud Spam filter. however was getting the below error:
The message couldn’t be downloaded either. Tried from Multiple pcs and still an issue
Trying the next day and the issue was fine which shows it must have been something on Barracuda’s side!
Changes to the Distributed File System (DFS) namespace are made on the domain controller with the PDC Emulator role. DFS root servers periodically request updated metadata from it. Inaccessibility of the PDC Emulator may result in incorrect operation of the DFS.
How to find you PDC
NetDOM /query FSMO
Recently during a DR test we spun up a file server that was protected using Microsoft Shared Cluster Services. The drives where mapped using a Physical Lun. Zerto protects this as long as you backup the Active Node of the cluster.
On Startup you need to change the VM Scsi mapping from Physical to None
Once booted , you should stop the Cluster Service and start is again with the /fixquorum flah
net start clussvc /fixquorum.
Now open the Cluster Manger and remove the Disks from the Server ( you will need to do this twice for each drive )
Once removed , stop the cluster service
bring Online the Disks in Computer manager.
If the disks come up as Raw , you will need to go back and perform a ReSync , then bring up again
For the trusted ips box to show up on the multi-factor authentication server settings in 365 multi-factor authentication so you can whitelist IP’s , you need to purchase and activate at least one single Microsoft Azure Multi-Factor Authentication License ( cheaper optoin ) or a single AD Premium License. This will give you the below options
trusted ips (learn more)
Skip multi-factor authentication for requests from federated users on my intranet
Skip multi-factor authentication for requests from following range of IP address subnets
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
- 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
