In monitoring we recently saw a Scheduled Task for a Shadow Copy Job failing with 0x2.

After running the Action manually in CMD I go the below error

C:\Windows\system32>C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=\\?\Volume{411116ac-84e511-11116-80d4-11111111111}\

vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Error: Either the specified volume was not found or it is not a local volume.

Running this in powershell listed all the Volumes with their current GID

GWMI -namespace root\cimv2 -class win32_volume | FL -property Label,DriveLetter,DeviceID,SystemVolume,Capacity,Freespace

Turns out the job was for a GUID that didn’t exist anymore on that system. After checking the other ShadowCopyVolume Tasks to make sure all the Disks were accounted for , I deleted the errored job

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 a user needed to Search another user’s 100GB Archive and Mailbox. Outlook search was taking far too long.

You can assign a user Permission to use the Content Search in  Security and Compliance Center  and limit access to a single Mailbox.

Assign Roles : 

In the Security and Compliance Center, Under Permissions,  Create a new Role with the following Roles assigned and add the User who needs to access

Assign Filter

This limits the users search scope to only a single Mailbox

Connect to 365 Security and Compliance Center :

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid -Credential $UserCredential -Authentication Basic -AllowRedirection Import-PSSession $Session -AllowClobber -DisableNameChecking

 

Add Filter

New-ComplianceSecurityFilter -FilterName MailboxFilter -Users pa@domain.com -Filters “Mailbox_DisplayName -like ‘John Smith'” -Action All

Wait around 10 minutes for this to apply then try logging in

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 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

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

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

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 when trying to login to a Citrix XenApp Server ( OS Server 2012 R2 ) users were getting a frozen Welcome Screen. The loading ‘Circle” would just stop and go no further.

Rebooting the cluster ( Datacollectors/Storefront and XenApp Servers ) did not resolve the issue. The session would start to load then go no further. I could login to the server via the console just not through the receiver.

Logging into the Data Collector I was greeted with 

“Trial Period Expired”

Checking the Licensing Tab showed no available licenses. I wasn’t able to check the original licenses so I created a temp account to setup a Trial License of 90 days

Create Trial Citrix Licenses

  1. Navigate to www.citrix.com and select Sign In (located in the upper right hand corner).
  2. Sign in using your My Account login credentials 
  3. Hover over the Downloads Tab and select Free Trials 
  4. Select the product you are trying to evaluate 
  5. Proceed to follow the prompts to request the product of choice 
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

 

$groups=Get-UnifiedGroup

foreach($group in $groups)
{
    Write-Host "************************************************"
    Write-Host "GroupName: "  $group.DisplayName
    Write-Host "Email: "  $group.primarySMTPAddress
    Write-Host "--- Members ---"
    $membersOfGroup=Get-UnifiedGroupLinks -Identity $group.Identity -LinkType Members
    foreach($member in $membersOfGroup)
    {       
        Get-Recipient -Identity $member.Name | select PrimarySmtpAddress |Format-Wide 
    }
     
}


$groups=Get-DistributionGroup

foreach($group in $groups)
{
    Write-Host "************************************************"
    Write-Host "GroupName: "  $group.DisplayName
    Write-Host "Email: "  $group.primarySMTPAddress
    Write-Host "--- Members ---"
    $membersOfGroup=Get-DistributionGroupMember -Identity $group.Identity
    foreach($member in $membersOfGroup)
    {       
        Get-Recipient -Identity $member.Name | select PrimarySmtpAddress |Format-Wide 
    }
     
}
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Upon trying to access Legacy Public Folders using 365 Webmail ( OWA ) the following error message is displayed

No public folders are available. Check that a public folders deployment exists in this Exchange Organisation
If so , please try again later

Solution:

You will need to use Outlook as per below

“In addition, users whose mailboxes are in Exchange Online won’t be able to access on-premises public folders using Outlook Web App”

https://technet.microsoft.com/en-gb/library/dn986544(v=exchg.150).aspx

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

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

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