Search This Blog

Wednesday, July 31, 2013

Default Computer OU in Active Directory

If you do not like that newly created computers in Active Directory goes into the folder Computers, you can change this with the command redircmp

http://technet.microsoft.com/en-us/library/cc770619(v=ws.10).aspx

First create the desired OU in Active Directory where you want your computers to go, here MyComputers:

image

Then change the default location to this new OU:

redircmp ou=MyComputers,dc=gt,dc=local

image

Now new computer domain members will go to this folder by default unless you specify another path on the domain join.

Wednesday, July 24, 2013

Active Directory Recycle Bin in Windows Server 2012

In Windows 2012 you don't need to use PowerShell to enable the recycle Bin, but please note that you can not disable it when first enabled. PowerShell is of course still possible to use Smiley

In Server Manager, select the Tools menu, and click Active Directory Administrative Center.

image

In Active Directory Administrative center select your local domain and click on Enable Recycle Bin.

image

Select OK to the warning about not being able to disable Recycle Bin after it has been enabled.

image

Select OK.

image

After a refresh you should see the container Deleted Objects.

image

And if you delete for example a user you will find it in this container, and be able to restore it to the old location or restore it to an other location.

image

Please note that the forest level must be Windows 2008 R2 to use the Recycle Bin.

Thursday, July 18, 2013

Link: Recommended hotfixes for XenApp

I would like to recommend this link http://support.citrix.com/article/CTX129229

[image%255B3%255D.png]

When building new XenApp 6.5 environments I always visit this page to see if the recommendations has changed since last time.

The page not only recommend Citrix hotfixes but also Microsoft hotfixes related to XenApp or RDS.

Thursday, July 11, 2013

Enterprise hotfix for Windows 7 SP1 and 2008 R2 SP1

lately I have noticed that some of my customers is unaware of the hotfix rollup Microsoft has released for Windows 7 SP1 and Windows 2008 R2 SP1.

The hotfix includes many of the fixes needed in an enterprise environment, so it might be a good idea to take a closer look on the rollup package.

http://support.microsoft.com/kb/2775511/en-us

image

Note that the package must be downloaded from Microsoft Update Catalog:

image

But as we all know nothing is as good ad it looks, apparently there are issues with the rollup package that need further investigation, so maybe it is good that the rollup package is not that commonly known or used Smiley

http://blogs.msdn.com/b/winsdk/archive/2013/05/13/roll-up-update-kb-2775511-reports-with-smb-2-0-data-truncation.aspx

 

Update 09-09-2013

The issue with the rollup package is now solved and we have no longer any excuse for not using the update, to many good thing in the update to ignore Smile

You must install this update after 2775511 - http://support.microsoft.com/kb/2732673 and also http://support.microsoft.com/kb/2728738

Update 21-01-2014

And now also http://support.microsoft.com/kb/2878378

Windows catalog links:

http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2732673

http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2728738

Thursday, July 4, 2013

Catch-all or super-subnet in sites and services

This is one of the small things that sometimes drag my attention.

A customer once asked me if it was possible to create a subnet in Active Directory that would catch all clients, and then still have some individual subnets defined for exceptions.

I must confess that I didn't know so I decided to try, but have never had a chance to report the result on the blog.

I created to sites SiteA and SiteB and created a DC in boot sites, then I created on subnet to catch all clients using ip addresses in 10.*.*.* pointing to SiteA:

image

Then I created a new subnet for a smaller subnet which was a subset of the catch-all subnet and pointed this to SiteB.

image

All clients clients on 10.*.*.* used SiteA except clients on 10.5.5.* which used SiteB as I had hoped for.

So it looks like it is possible to have a kind of wildcard subnet to catch all subnet that you might get in the future and decide the default site for those new subnets.

The use of the catch-all subnet will off course depend on your IP-addresses in use, and still require subnets to be created if the default Site is not the right one.