Re: Adding PC to Domain. What really happens
- From: "Richard G. Harper" <rgharper@xxxxxxxxx>
- Date: Mon, 1 Aug 2005 17:41:57 -0400
The correct answer is, "Who can tell?"
There is at least one GPO being applied to the computer - the default domain
policy, unless you've deleted it or removed it from the domain container.
Additionally, your domain user may have rights that your workgroup user
doesn't, or vice-versa.
Try using the RSOP.MSC (Resulting Set of Policies) tool to compare
permissions and settings when on the domain and off the domain and you'll
likely find your problem quite quickly.
--
Richard G. Harper [MVP Shell/User] rgharper@xxxxxxxxx
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
"Drumgod" <Drumgod@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE66058D-D1DF-436E-8AEC-BBE4805BC1E7@xxxxxxxxxxxxxxxx
> All,
>
> I am having a problem with a company application. Seems that it will work
> if
> I add it to a test domain, but not under a workgroup environment. It's a
> client / server type app. Oddely enough, when I remove the workstations
> from
> the domain , the application stays functional (NO GPO's are being
> applied!!)
>
> My question is ? Does anyone know what happens / changes to the system
> when
> its added to a domain. Im looking for a technical artical (MS or KB) that
> describes any changes made to the system when joining the domain. I.E
> Registry, files, permissions, local GPO's . . ect.
>
> TIA
>
> Drum on .. .. . . .
.
- References:
- Adding PC to Domain. What really happens
- From: Drumgod
- Adding PC to Domain. What really happens
- Prev by Date: Re: Can't connect to msn.
- Next by Date: Re: No Broadband Internet access via router on home network
- Previous by thread: Adding PC to Domain. What really happens
- Next by thread: Can't connect to msn.
- Index(es):
Relevant Pages
|
