Re: Manage AD computers based on AD Sites and Services
- From: "Joe Richards [MVP]" <humorexpress@xxxxxxxxxxx>
- Date: Mon, 26 Jun 2006 16:01:29 -0400
So make it a requirement for people to move the computer from one OU to another when they move the PC. This is a policy problem or an app design issue. I would lean towards the app design issue but haven't done anything with WSUS so don't know if it could be done more intelligently.
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Rhidian wrote:
Thanks for that Joe- it's a shame as WSUS and our AV solution both rely on PCs getting app-specific information from the "local" OU.
If anyone else has any information it'd be great- for example, a PC in "Denver" gets it's WSUS information from a Denver-specific OU group policy, then someone switches it off and moves it to Miami... it's still trying to pull all it's WSUS data from Denver, except our bandwidth can't cope ! We can do the OU movement manually but it's an admin overhead (besides which, we have trouble telling if PCs are just switched off, if they've been moved, rebuilt etc etc...)
- References:
- Re: Manage AD computers based on AD Sites and Services
- From: Joe Richards [MVP]
- Re: Manage AD computers based on AD Sites and Services
- Prev by Date: Re: Force the preferred Server for Users
- Next by Date: Re: DR - Active Directory
- Previous by thread: Re: Manage AD computers based on AD Sites and Services
- Next by thread: Re: Detailed Description needed on Domain Join internal Process
- Index(es):