To Recreate SysVol Share

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following subkey in Registry Editor:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
  3. In the details pane, right-click the SysvolReady flag, and then click Modify.
  4. In the Value data box, type 0, and then click OK.
  5. Again in the details pane, right-click the SysvolReady flag, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

The NetLogon Share is actually the Scripts folder that sits in this Folder , so is this Sysvol folder is still blank if means your replication is not working

In the Event Log : Applications and Services Logs/DFS Replication in Event Viewer:

Check for Event ID’s 2010 or 4114 ,

 

set msDFSR-Enabled to FALSE

DFSRDIAG POLLAD 

set msDFSR-Enabled to TRUE

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
  1. Start the Windows Service : Windows Audo and make sure its set to Automatic
  2. Enable the following group policy on the machine

    Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection\Allow audio and video playback redirection.

Log off then back on and it should work

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

When few users were trying to connect to a Citrix netscaler internally they were getting an error

socket error 10060

If you use the ICA file to check what server the machine is trying to connect to ( Go in %TEMP% and open up the latest .ica file in Notepad ) 

Check the machine can ping the server , maybe a networking ussue

Check if the server has been cloned and was using the same ID as another one ( putting it in Maintenance mode fixed the problem ) 

 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
for /f "delims=" %d in ('dir /s /b /ad ^| sort /r') do rd "%d"

(if used inside a batch file, replace %d with %%d)

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 we have a Virtual Machine that was stuck on booting on Please Wait

We had to boot the server into Safemode by holding down the f8 key on startup and choosing safemode which got the machine to the login prompt and reboot

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

Download and Run the “Digicert Certificate Utility: and go to Tools , then Check Install

Enter the URL link and make sure the URL is coming back with 2 Certs , the top one should be your cert and there should be a Root Cert underneath

If one one cert if coming back , go into your Netscaler , Go to Configuration , Traffic Management , SSL , Certificates, Server Certificates and Link your SSL Cert there to a root one by right clicking and choosing Link

A manual way

Export the .cer files for the certificate using Internet Explorer ( Run as Administrator to Copy to file otherwise it will be greyed out ) and also the Root CA for that cert

Put these somewhere the Mac can access like a dropbox folder

Install the Certs to the Mac’s keychain

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

Error: Unable to find SRA files. You must install SRA before adding or modifying an array manager.

Troubleshooting steps:

1.Took RDP to both the SRM servers.
2. Reset the administrator@vsphere.local passwords for both the VCs.
3. Performed Modify/install on both the SRM servers.
4. Reconfigured array pairing by typing the pureuser ID and password.

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 using Windows 10 or have Powershell 5 installed run

Install-Module AzureRM

Once installed, use the following to log into Azure in an interactive fashion:

 
Login-AzureRmAccount

Edit these lines , use Get-AzureRmVirtualNetwork to get your VirtualNetwork Name

Run these 

$vmName = “%vmname%”
$resourceGroupName = “%resourcename%”

$virtualNetworkName = “%virtualnetworkname%”
$locationName = “australiaeast”
$vmsize = “Standard_A1”
$destinationVhd = “https://vmname.blob.core.windows.net/vhds/osdisk.vhd”

$virtualNetwork = Get-AzureRmVirtualNetwork -ResourceGroupName $resourceGroupName -Name $virtualNetworkName
$publicIp = New-AzureRmPublicIpAddress -Name $vmName -ResourceGroupName $ResourceGroupName -Location $locationName -AllocationMethod Dynamic
$networkInterface = New-AzureRmNetworkInterface -ResourceGroupName $resourceGroupName -Name $vmName -Location $locationName -SubnetId $virtualNetwork.Subnets[0].Id -PublicIpAddressId $publicIp.Id
$vmConfig = New-AzureRmVMConfig -VMName $vmName -VMSize $vmsize
$vmConfig = Add-AzureRmVMNetworkInterface -VM $vmConfig -Id $networkInterface.Id
$vmConfig = Set-AzureRmVMOSDisk -VM $vmConfig -Name $vmName -VhdUri $destinationVhd -CreateOption Attach -Windows
$vm = New-AzureRmVM -VM $vmConfig -Location $locationName -ResourceGroupName $resourceGroupName

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

I was trying to copy an Azure VM Hard Drive from a classic storage account to a new storage account , however after shutting down the VM I was getting the error

Copy status: Failed; Description: 412 ConditionNotMet “Copy failed when reading the source.”.

I contacted Azure support who notified me to use the below

VHD is attached to VM, and then you can refer to the following steps to copy it:

  1. Download and install  Microsoft Azure Storage Explorer.
  2. Click Storage accounts on the left pane on Azure Portal> Click on the name of the corresponding storage account>Keys>Copy the primary key
  3. Open the tool Azure Storage Explorer, and follow the steps below to connect to the target and destination storage accounts

After both storage accounts get connected, you can go find the corresponding vhd file and copy it, and then go to the destination container of the storage account to paste the copied file

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