WMI Filter for Windows Operating Systems

You can use the attached queries to apply GPOs only to a specific Operating System. This can prevent problems, like applying a server GPO to a client and vice versa. You can also use this, to only apply mappings on client OS.


Windows Server 2012 DC
select * from Win32_OperatingSystem where Version like "6.2%" and ProductType = "2"

Windows Server 2012   
select * from Win32_OperatingSystem where Version like "6.2%" and ProductType = "3"

Windows 8   
select * from Win32_OperatingSystem where Version like "6.2%" and ProductType = "1"

Windows Server 2008 R2   
select * from Win32_OperatingSystem where Version like "6.1%" and ProductType = "3"

Windows Server 2008 R2 DC   
select * from Win32_OperatingSystem where Version like "6.1%" and ProductType = "2"

Windows 7   
select * from Win32_OperatingSystem where Version like "6.1%" and ProductType = "1"

Windows Server 2008   
select * from Win32_OperatingSystem where Version like "6.0%" and ProductType = "3"

Windows Server 2008 DC   
select * from Win32_OperatingSystem where Version like "6.0%" and ProductType = "2"

Windows Vista   
select * from Win32_OperatingSystem where Version like "6.0%" and ProductType = "1"

Windows Server 2003   
select * from Win32_OperatingSystem where Version like "5.2%" and ProductType = "3"

Windows XP   
select * from Win32_OperatingSystem where (Version like "5.1%" or Version like "5.2%") and ProductType = "1"

Windows Server 2012 Core Network Companion Guide: Group Policy Deployment

Hi guys,

Microsoft released a guide for deploying GPOs via group membership.

"This guide provides instructions for deploying Group Policy settings to a set of client computers or users by using membership groups rather than account location in the OU hierarchy of a domain."

You can download this guide here.

Roaming profile users experience slow logons on Windows 7

SYPTOMS:
Roaming profile users experience slow logons on Windows 7.


RESOLUTION:
- Check the network cables, workstation hardware etc. and change it if required.

- Check the size of the profile (Create Quotas via Policy) and delete some files.

- Check if the correct network card drivers are installed on affected workstations.

- Check if the network path is working in your policy or user object defined for Roaming Profile.

- Check the permissions on the Server are set right.

- Check this hotfix if you implemented the described scenario in the MS article.


 STEPS FOR THE FUTURE:
- Exclude some folders from roaming to reduce the profile size
Apply the following settings via GPO:
GPO Path: "User Configuration/Policies/Administrative Templates/System/User Profiles"
"Exclude directories in roaming profile" set to "Enabled"
For example type in the following: AppData\Roaming\OpenOffice.org

 - Create Quotas via Policy
GPO Path: "User Configuration/Policies/Administrative Templates/System/User Profiles"
Set the settings for the Policy "Limit profile size"

WDS Error: "PXE-E55: ProxyDHCP service did not reply to request on port 4011"

Hi guys,

if you getting this error, on the PXE Boot, it could be that your workstation is saved on a WDS database for rejected and approved devices. To delete this entries you can run the following commands on your WDS server.

Wdsutil.exe /delete-autoadddevices /devicetype:rejecteddevices
Wdsutil.exe /delete-autoadddevices /devicetype:approveddevices


Now you are able to image the affected workstations.