Blog about Microsoft Server products
TwitterFacebookLinkedIn

@GJohansson

TwitterFacebookLinkedIn

GJohansson - Can't help to like the new face of @Office365 after upgrade. Me like! Smoooooth 2 days ago

BPA: Protected from accidental deletion

If you like me want to clear BPA errors and you get this on your AD-server:

Title:
All OUs in this domain should be protected from accidental deletion

Severity
Warning

Date:
2013-05-21 06:16:50

Category:
Configuration

Problem:
Some organizational units (OUs) in this domain are not protected from accidental deletion.

Impact:
If all OUs in your Active Directory domains are not protected from accidental deletion, your Active Directory environment can experience disruptions that might be caused by accidental bulk deletion of objects.

Resolution
Make sure that all OUs in this domain are protected from accidental deletion.

http://go.microsoft.com/fwlink/?LinkId=142204

Just do:

Get-ADObject -Filter ‘ObjectClass -eq “organizationalUnit”‘ | Set-ADObject -ProtectedFromAccidentalDeletion $true

Easy Ler

Export/Import DHCP 2012

Nowadays everything is going to be PowerShell but since I was working with 2003 servers and not sure about PS-support I was going old style with migrating DHCP from Server 2003 to 2012

Thought I just share howto as a future reference (yepp, there is more 2003-servers out there Ler)

On Server 2003

netsh dhcp server export C:\Temp\dhcp_config.dat all

Unauthorize the DHCP and stop DHCP Service

On Server 2012

Install and Authorize DHCP
In elevated cmd:

netsh dhcp server import C:\Temp\dhcp_config.dat all

Restart DHCP Service

I know I should do more PS but can’t help liking old black window style Skrattar

Why don’t I see all GPO settings on my Windows Server 2012

This seems as a fairly common question so I’ll post it here for future references.

This is same thing for Windows 7/Server 2008 (not sure when they changed this).

Anyway Server 2012 contains all admx files for, you got it right, server.
And therefore Windows 8 contains all admx-files for, right again, client.

This means that when you start with let’s say Server 2012 and want to configure settings for clients you will miss out a lot of settings as the server do not contain all settings that applies to client and vice versa.

What you need to do and maintain for the future is to create a Central Store for adm/admx-files so that any client or server that “creates” GPO’s use the same templates and that you really get all settings available.

Basically you create a folder named “PolicyDefinitions” in \\corp.domain.com\SYSVOL\corp.domain.com\policies and put your admx and adml files here.
Easiest of course is to copy from C:\Windows\PolicyDefinitions on both a client and server to get files from both sides.

MS KB: http://support.microsoft.com/kb/929841

Yes, it does say “Applies to Vista” but this is same for any OS after Vista was released.

Windows 8 GPP Drive Maps failed finally solved

Microsoft now finally released a hotfix that solves the problem.

It’s released with KB2795944 which includes a fixed version of gpprefcl.dll that is used for when GPP creates drive maps.

As said before this only is a problem when you’re domain user is also local administrator on your computer and using GPP Drive mappings with reconnect option (persistent mode).

After you apply the hotfix you need to restart your computer.
Enable persistent mode on your drive mappings.

You can use this command in cmd.exe to see that you’re drives are truly using persistent mode (you have go offline first to see that it uses persistent mode):

wmic netuse

Previous posts:
http://gjohansson.com/blog/2013/01/20/followup-win-8-gpp-drive-maps-fails/
http://gjohansson.com/blog/2012/08/22/windows-8-gpp-drive-maps-fails/

Happy updating and please like/share my post to spread the word.

I would like to get your comments if you have any Smile

Windows Server 2008 R2 RDP stops after SP1

Microsoft released some time ago hotfix KB2667402. If you install Service pack 1 on your system after this hotfix has been applied a Rdpcorekmts.dll is then installed which makes RDP unavailable to the system.

To solve the situation you need to get local access to machine so replace the faulty dll-file.

Easiest solution to the problem is to uninstall KB2667402 and then re-install again so it updates the dll to file version 6.1.7601.17767

This is also stated as a known issue on the KB page which also informs the problem exist on Windows 7 if you try to RDP.

This has been informed by others before regarding this issue but we did not encounter it until today.