Friday, November 18, 2016

How to enable PAE On Windows Server 2008 Standard 32bit increasing RAM from 4GB to above

How to enable PAE on Windows Server 2008 Standard 32-Bit
1.  Log in to the server
2.  Once logged in, click on START, Right click on command prompt icon and choose Run as administrator

3.  Once command prompt opens, type bcdedit /set pae forceenable then press enter.  Command should successfully complete without any errors.
6.  Restart server.
7.  Once server restarts, open task manager, click on Performance tab and check Physical Memory.
8.  Done!

Monday, November 14, 2016

How to enable container option using ADSIT Edit tool


 How to enable container option using ADSIT Edit tool
You need to create Active Directory Container. In this case the most people probably thinking is that they have to create an OU (Organizational Unit), but that is not the case.
There are a few differences between an Active Directory Container and an Active Directory OU. The main difference is that Group Policy Objects (GPO) cannot be applied to a container.
The Active Directory Users and Computers program will not give the option the create Container objects by default (right click, new). But with the following procedure, you can enable this. (You have to be member of the “Schema Admins” security group)
Open “Adsiedit.msc”, richt click “ADSI Edit” and click on “Connect to…”


 Select “Schema” by “Select a well known Naming Context” and press the “OK” button
 
In the left plane select “Schema,CN=Configuration,DC=domain,DC=lan” and look in the right plane for “CN=Container”. Open its properties.

 Change the value of “defaultHidingValue” to “FALSE” and press the “OK” button.


 Open the Active Directory Users and Computers program (check if Advanced Features are visible), right click on the domain name or any Container/OU and select the “New” option. The Container option is now also listed in the list of objects.


 It’s done.

Monday, October 31, 2016

Licensing mode for the Remote Desktop Session Host is not configured

Licensing mode for the Remote Desktop Session Host is not configured

How to fix RDS 2012r2 error: “Licensing mode for the Remote Desktop Session Host is not configured.”

Remote Desktop Session Host (RD Session Host) enables a server to host RemoteApp programs or session-based desktops. Users can connect to RD Session Host servers in a session collection to run programs, save files, and use resources on those servers.
We recently solved a known issue related to the licenses required to connect to a Remote Desktop Session Host server or a virtual desktop. The error description reads: “Licensing mode for the Remote Desktop Session Host is not configured.”
Licensing mode for RDS Host server is not configured resized 600
We developed a fix for the licensing issue with RDS on server 2012r2. We found some solutions for this known bug but none that actually worked. Incidentally, deleting the GracePeriod key like many forums said didn’t fix the problem.

To fix the problem, run the following commands in powershell to set the licensing server properly on the rd session host using the WMI CIM provider:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj. SetSpecifiedLicenseServerList("licserver.domain.local")

Then, go into the registry and manually set the licensing mode:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core\LicensingMode

You need to change the DWORD to 2 for Per Device or 4 for Per User.
Licensing Mode in Registry Editor
Next, reboot the system. The changes made previously will report everything properly and the RDS host will now recognize the licensing configuration.