Following the guide found in the blog post below;
https://blogs.aws.amazon.com/security/post/Tx71TWXXJ3UI14/Enabling-Federation-to-AWS-using-Windows-Active-Directory-ADFS-and-SAML-2-0
This guide allowed us to set up federation using ADFS 3.0. The only thing to note which does not appear to be in the blog post, is that the Active Directory Security Groups that you create (starting AWS-) must be Global or Universal. This will not work if the group has been created as Domain Local.
If you have created the group at this level you can change this without needing to recreate the Security Group. Simply set the Group Scope to "Universal" as this will then allow the "Global" box to be selected again.
This will also accept nested groups when granting access so you do not need to add all users individually.
When attempting to upload files to a storage account in Azure, if you upload using the portal no Check-MD5 value appears to be generated. In order to have a value generated you need to use the AzCopy tool.
Once you have this installed, open a command prompt and run the tool (default installation location will be C:\Program Files (x86)\Microsoft SDKs\Azure\AzCopy\AzCopy.exe)
To upload a single file to a location, use the following command;
AzCopy /Source:A:\Folder\On\My\Computer /Dest:https://storageaccount.file.core.windows.net/filescontainer/folder /DestKey:Storage-Account-Access-Key /Pattern:FileName.ext
Replace the bold text with your parameters
/Source: needs to be the folder location only - do not include the file name or the command will fail. The file name is specified in /Pattern:
Update:
Alternatively, if you have several files to upload to a single location and so want to copy the entire contents of a folder, you can run the command below. This copies all content in a directory including structure;
AzCopy /Source:A:\Folder\On\My\Computer /Dest:https://storageaccount.file.core.windows.net/filescontainer/folder /DestKey:Storage-Account-Access-Key /S
Running ESXi 5.0.0 with command line access the following commands will restart the management agents - logged in as root;
/etc/init.d/hostd restart/etc/init.d/vpxa restart
This was required when the host stopped reporting it's CPU and Memory usage in vSphere Client.
After adding some additional sites to the "Use Policy List of Internet Explorer 7 sites" policy in Group Policy we found that these sites were not running in compatibility view for the user despite RSOP reporting that the policy was in place, and the user's registry reporting the same.
(Registry key can be found at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\BrowserEmulation\PolicyList)
There is a known limitation in IE11 whereby it doesn't run sites presented from this policy. Instead if you want to enable compatibility mode via GPO you need to turn on Enterprise Mode.
The TechNet document below gives the steps to deploying from GPO, as well as creating a registry entry to test with a single user.
https://technet.microsoft.com/en-us/itpro/internet-explorer/ie11-deploy-guide/turn-on-enterprise-mode-and-use-a-site-list
If you turn Enterprise Mode on and still cannot select it from the "Tools" menu in IE11, chances are you are missing update 3087038 (KB3089548). If this is not installed you will not be able to turn on Enterprise Mode in the browser.
More information on this update can be found at
https://support.microsoft.com/en-us/kb/3089548
The update itself can be downloaded from
https://technet.microsoft.com/library/security/MS15-094
Once this is installed you should be able to use Enterprise Mode to view sites that require compatibility.
To create the XML file containing sites to be displayed using Enterprise Mode download the Enterprise Mode Site List Manager tool from https://www.microsoft.com/en-us/download/details.aspx?id=42501
I had a requirement to convert a large number of automatically created DNS "A" records into static entries to avoid issues with DNS scavenging. Rather than manually creating a static record then removing the existing one, this can be accomplished with a few clicks.
1. In "DNS Manager" select "View" > "Advanced"
2. Browse into the appropriate "Forward Lookup Zone" and select the "A" record you wish to convert to static.
3. Double click the record (or right click and select "Properties") and uncheck the "Delete this record when it becomes stale" tick box.
4. Click OK.
When you refresh the page you'll now see the time stamp has been removed from the record and is instead set to "Static"
In order to check which features you are licenced for on your 3PAR, open a connection to the CLI and run the command;
showlicense
You should see a response similar to;
License key was generated on date
License features currently enabled:
Dynamic Optimization
InForm Suite
System Reporter
Thin Conversion
Thin Copy Reclamation
Thin Persistence
Thin Provisioning (44032G)
Virtual Copy
To find out which version of PowerShell you are using, run the following in PowerShell;
$PSVersionTable.PSVersion
You will get an output similar to;
Major Minor Build Revision
----- ----- ----- --------
5 0 10586 117
