Question about fresh install of server 2003.

I have been installing a couple of pc's with Server 2003 for testing purposes. The question i have is this.

I have joined the servers to our current domain but only has member servers, i log on as domain admin and set the desktop background of what I want from a couple of pic files on the c: drive. Trouble is that every time i reboot i loose the desktop and the IE securty pop up comes up again as if its the first time i have logged on(even though i put the tick in the box not to)

It is strange to me, have i missed somthing simple? Its the desktop thats buggin me!

Sorry if this is a bit basic but I don't normally get chance to play with the servers.

Try using a bitmap if your not see if it makes a difference.

Does the domain admin account have a roaming profile set?

I can think of 3 things:

1) Its a roaming profile and its not a bitmap you are using as a background. This is an issue in XP, not sure about 2003.

2) Check for any userenv errors in the event log, something may be keeping the registry open when you logout so changes are not saved.

3) Some version of the Nvidia driver stop the profile from being written. (Odd I know, spent AGES finding this one on my home computer).

Might also be GPO's overriding things.

Does sound like a GPO setting somewhere- perhaps the default domain controller policy if you are placing your member servers in that OU, or even a top level policy at some point. Run an RSOP on your server to see which are applying.

What I try and do is make a "Member Server" top level OU that I can create and link GPOs to apply to, and then have a "Print Server" OU underneath (or whatever else); that way you can control the GPOs that apply to your member servers without tinkering with the default domain or domain controller policies (could be bad).

As I said, open up the command line and type:

gpresult.exe

See what it says about which are being applied.

Sorry for the broken nature of the post...just got up :-)

Paul

I think it could be the GPO as well

I keep virtually everything in a sub OU for the domain, special groups, member servers etc are kept at the root level still. I never edit default domain policy, so I didn't even think about it being a gpo problem :P

if in doubt, create and ou called "member servers" then block inheritence on the ou (i do this anyway and write a custom gpo for member servers.)