A run through of installing Windows 10 Server so you know what to expect (though if you’ve installed Server 2012 before this will be old news). This is Build 9841- 2 October 2014
I’ve recently been involved in setting up a number of SaaS applications for my organisation which use our on-premise Active Directory to authenticate users. Whilst most of the time constructing a LDAP Distinguished Name from an AD tool such as Active Directory Users and Computers is straightforward, it’s easy to mis-spell an OU or miss out a layer in a complex hierarchy.
The right tool for the job is ADSI Edit -“Active Directory Services Interface”. This provides the full Distinguished Name for every object- be it an Organisational Unit, User, Computer, Group, Organisational Unit etc. which can be copied from the listing.
The ADSI Edit Window
For more information about ADSI Edit- visit the Microsoft TechNet Pages.
Some PowerShell to find all the VMs in an ESX environment which are powered on and running Windows XP or Server 2003.
In my VMware ESX environment I have a number of virtual machines still running Windows XP or Server 2003- usually performing very specific tasks or allowing access to legacy applications, but still part of the production environment. With the recent End of Support for Windows XP and the upcoming one next year for Server 2003 I need to look at each of these VMs and see if they can be upgraded or decommissioned. Listing these in the GUI is fiddly at best- I want VMs with one of these two OSes, from any datacentre and I only care about VMs which are powered on. So, PowerCLI to the rescue:
.PowerState -eq "PoweredOn" -and
.Guest -like "*Windows XP*" -or $_
.Guest -like "*Server 2003*")} |
MyServer1 Microsoft Windows Server 2003 Standard (32-bit)
MyServer2 Microsoft Windows Server 2003 Standard (32-bit)
MyServer3 Microsoft Windows Server 2003 Standard (32-bit)
MyXPVM1 Microsoft Windows XP Professional (32-bit)
MyXPVM2 Microsoft Windows XP Professional (32-bit)
Not the most complicated piece of scripting, but it’s answered my question and I can refer back to it as upgrades continue to see what systems remain.
Not an everyday task this (once you’ve checked it you can usually remember what the level is!), but here’s how to find the Domain Functional Level of your Active Directory domain and whilst there check for any trust relationships with other domains.
When deploying a printer by Group Policy using the Windows Server 2008 R2 “Print Management” application on a Windows Server 2003 Active Directory the following error may appear.
Deploying printer connection ‘\\server\printer’ to per machine GPO ‘GPO_Name’ failed. Please make sure that the schema on the Active Directory domain controller has been updated to support printer connection settings.
This can be resolved by Continue reading