If you try to RDP to a machine, but can’t because you receive the error below, you can use PSExec to remotely disable the requirement for NLA.
“The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”
Download PSExec from TechNet. Run the code below updating the following values.
\\VMNAME – The name of the machine on which you want to disable NLA
VMNAME\ADMIN_ACCOUNT – The username of a local administrator on the machine on which you want to disable NLA, e.g. pc1\admin
psexec \\VMNAME -u VMNAME\ADMIN_ACCOUNT -p PASSWORD reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp” /f /v SecurityLayer /t REG_DWORD /d 0
Power Map, which is part of Microsoft’s Power BI, requires an Office 365 version of Excel. When attempting to install Excel via Office 365 on a server I ran into the error:
Error Code 30125-4 when installing Office 365 Something went wrong. Sorry, we ran into a problem
Although the proxy was configured in Control Panel -> Internet Options, I had to enable the proxy via an elevated command prompt. Type: netsh winhttp set proxy %Address of proxy server% bypass-list=(local)
This will configure the proxy server and setup proxy bypass for local addresses.
This is a quick post to describe the process of creating a dedicated account for joining machines to an Active Directory (AD) domain. This is useful for things like System Center Configuration Manger task sequences and System Center Virtual Machine Manager templates.
First create a standard Windows user account. Next, right-click on the Computers Organisation Unit (OU) within your AD domain. From the menu choose Delegate Control…
On the next screen (Users or Groups) choose Add and select the user account you just created. Click Next. Choose “Create a custom task to delegate” on the next screen.
Next, choose to only delegate control to computer objects and tick Create and Delete selected objects in this folder. Click Next.
On the next screen choose to show general permissions and from the list select:
- Reset password
- Read and write account restrictions
- Validated write to DNS host name
- Validated write to service principal name
Click Next and finish to complete the wizard. Repeat this process for any other OUs where you’ll be joining computers to the domain.
Adding AD users to the local administrators group on multiple computers is simple using Group Policy. In this post I’ll describe the process.
Create a fresh group policy object (GPO) and link it to a test Organisation Unit (OU). Add a test server to the OU.
Open the GPO and navigate to Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Restricted Groups.
Right click and choose Add Group. If you want to add users to the local administrators group enter Administrators. In the next window under “Members of this group:” click Add and choose the users to add to the local administrators group. Note that any users that are currently in the local administrators group will be removed and replaced with the users you select here. If that is what you want click OK and close the GPO.
The second method allows you to add an AD security group to the local administrators group. This process is additive and users and groups that are currently in the local administrators group are untouched.
Navigate to Restricted Groups as previous, right click and choose Add Group. This time enter the name of the AD security group you wish to add to the local administrators group. Click Ok and on the next screen in the “This group is a member of:” section click Add. Enter Administrators to add the group to the local administrators group. Click OK and close the GPO to save changes. You can add additional users to the domain group and they will automatically be part of the local administrators group on servers that apply the GPO.
Three old virtual servers were showing as VM Additions Not Detected in System Center Virtual Machine Manger 2012 SP1 (VMM).
Choosing to Install Virtual Guest services didn’t resolve the problem as they were already listed in Add Remove Programs and installed. Mouse integration was working without having to use CTRL-ALT-LEFT, but I was unable to use the Shut Down command from VMM.
Device Manager showed no errors, but the Event Log was showing errors for the failure of the following services to start: Hyper-V Heartbeat, Hyper-V Data Exchange, Hyper-V Guest Shutdown, Hyper-V Time Synchronization and Hyper-V Volume Shadow Copy Requestor.
A closer looked showed two Hyper-V integration components entries in Add Remove Programs: Hyper-V Integration Services (version 6.2.9200.16384) and Microsoft Hyper-V Guest Components.
I chose to uninstall both components. Following a reboot I re-installed the Hyper-V Integration Services using VMM. Following this everything worked correctly.
In Windows Server 2012 the binaries for Features on Demand e.g. the .Net Framework 3.5 are not installed as part of Windows. When you enable this type of feature Windows will attempt to contact Windows Update to download the required files. If you’re working on a server that’s not connected to the internet this can be problematic. One work around is to use Group Policy to specify an ISO file as an alternate file source.
Mount the Windows Server ISO into the virtual machine
Open the local Group Policy editor by typing gpedit.msc at the Start Screen
Navigate to Computer Configuration -> Administrative Templates -> System
Open the “Specify settings for optional component installation and component repair” setting
Enable the setting and type the path to the sxs folder on your ISO file.
View this KB for further information http://support.microsoft.com/kb/2734782/en-gb
Office 2010 is installed as part of our standard Windows 7 System Center Configuration Manager (SCCM) task sequence. Office installed correctly all our PC models except the Dell Latitude E6320 and E6330. These models rebooted during the Office installation, stopping the task sequence and leaving the laptop unusable. If you have the same problem the resolution is easy.
Open your existing MSP file that controls the Office installation by running Setup.exe /Admin.
Open the “Modify Setup properties” section and add a new property. The property name needs to be SETUP_REBOOT and the value Never.
Save your changes to the MSP and Office will no longer reboot.