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
Error: Unable to find SRA files. You must install SRA before adding or modifying an array manager.
1.Took RDP to both the SRM servers.
2. Reset the firstname.lastname@example.org 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.
If you are using Windows 10 or have Powershell 5 installed run
Once installed, use the following to log into Azure in an interactive fashion:
Edit these lines , use Get-AzureRmVirtualNetwork to get your VirtualNetwork Name
$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.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
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:
- Download and install Microsoft Azure Storage Explorer.
- Click Storage accounts on the left pane on Azure Portal> Click on the name of the corresponding storage account>Keys>Copy the primary key
- 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
Make sure your Avaya phone system has been setup with a routeable DNS Server per http://pariswells.com/blog/random/avaya-ip-office-default-gateway
Create a user in 365 with a License
On the IP Office under the SMTP Tab put the following:
Server Address – smtp.office365.com
Port – 587 – Mine was intermittently working with 25 so I switched it and it has worked on 587.
Email From Address – email@example.com
Use STARTTLS – Checked
Server Requires Auth – Checked
Username – firstname.lastname@example.org
Password – admin accounts password
Use CRAM-MD5 – Unchecked
Identified that the CITRIX XTE SERVER service terminated unexpectedly.
- Renamed the httpd.conf file in this directory C:\Program Files (x86)\Citrix\XTE\conf
- Copied the httpd.conf file from a working server
- Restarted the Citrix Xte Server Service
New sessions and existing sessions can now be established
Current investigating the cause of the issue to ensure it will not happen again
You can use CloudWatch Alert per below with SNS Topic