What are the less obvious effects of adding a PC to an AD domain?
- From: samiam@xxxxxxxxxxxxxxx
- Date: 31 Dec 2006 14:45:09 -0800
Hi,
What are the less obvious effects of adding a Novell PC to an AD
domain? I am just wondering what considerations I am missing. The
obvious effects are:
-That machine will get a logon prompt with a choice to sign onto the AD
domain, Novell Domain or to the workstation
But if the machine doesn't logon to the AD domain, does joining the AD
domain have any effect before it's logged onto the AD domain?
What about after the PC DOES logon to the AD domain? The obvious:
-A new domain profile is applied
-The PC can access domain resources and GPO's can be applied.
What is less obvious?
At the enterprise level, in a situation where the PC's are mostly not
going to log onto the AD domain, though some will, how will joining
them to the AD domain (which we need to do for certain application
compatibility) effect them?
Thanks for taking the time to shed some light.
L,
S
.
- Follow-Ups:
- Re: What are the less obvious effects of adding a PC to an AD domain?
- From: Herb Martin
- Re: What are the less obvious effects of adding a PC to an AD domain?
- Prev by Date: Joining 500 Novell PC's to AD Domain - can I turn off all default AD GPO's?
- Next by Date: Re: Group policy & user profile login script execution
- Previous by thread: Joining 500 Novell PC's to AD Domain - can I turn off all default AD GPO's?
- Next by thread: Re: What are the less obvious effects of adding a PC to an AD domain?
- Index(es):
Relevant Pages
|
