Can't delete Default User profile in NETLOGON

Microsoft Windows server 2003 r2 standar...
January 25, 2010 at 07:42:05
Specs: Windows 2003 R2 Server, XP clients, 2000 clients
I can't delete/rename/move the Default User directory in the c:\windows\sysvol\sysvol\domain\scripts directory. I want to create a new default profile but it won't let me write anything to the current one. It tells me to delete it and try again, but I can't delete it. HELP!

See More: Cant delete Default User profile in NETLOGON

Report •

January 25, 2010 at 07:51:12
Wait a minute, the profile in sysvol folder? Something isn't right here... perhaps you meant you're trying to edit a script?

Report •

January 25, 2010 at 08:15:42
Well it's in the scripts folder but it is the copy of the default user profile I want to load when users log onto the network for the first time. It worked fine when I created it but I forgot to put a few things in it so I made the changes to the local profile on a client machine I'm basing it on but I can't save the updates to it. I get a message that says to delete the Default User folder in NETLOGON which is the share of the path I mentioned above and try again to copy the profile I want. This is also the solution I'm finding on tech advice forums and MS But I can't delete it or rename it or move it.

Report •

January 26, 2010 at 06:02:40
I see what you're trying to do, and I'm not surprised you get that message... as default the sysvol folder is a non-write folder for everyone except administrators.

Try moving your profile folder to another shared folder that users have write access to. I see no advantage in having the template profile in the sysvol folder.

Report •

Related Solutions

January 26, 2010 at 06:58:20
I was logged on as the administrator and it wouldn't let me delete it. I rebooted the server and was able to delete it then.

Anyway, I'm not sure why you say not to put it in the \\DomainController\SYSVOL\DomainName\Scripts\Default User
path. That is where it needs to be for it to function as a default user profile. That path is shared on the network as NETLOGON which is where I save it from the client computer (logged in as administrator) but the actual storage path of it is \\DomainController\SYSVOL\DomainName\Scripts\Default User

I'm getting this info from

Report •

January 26, 2010 at 23:29:25
Ok the last post in the link you referred to shed some light on what you're aim is. And if that is really the procedure MS wants you to do I can't say anything about it. But it's still not the way I would, or am doing it.

The reason they want you to put the 'default user' profile in the netlogon folder is because it's read-only, so the client cannot change the profile, and the next 'default user' won't get a different profile.

But there is still nothing stopping you from making the exact same setup with an entirely different folder. I think you should explore different methods and see if you can find out what happens. Start out copying the profile to another folder, and share it with full rights. See what happens. Then change the folder to read-only. Maybe you can figure out why the first setup didn't work that way.

Report •

January 27, 2010 at 05:49:30
Once I deleted the original folder I made and recreated it, it worked fine. I think what happened is when I made the changes and tried to save them to the original folder, it deleted most of the settings in an attempt to overwrite, encountered locked files it couldn't delete and recreate so the process errored out, and then the default no longer functioned like it was supposed to because half of it was missing.

I'm not sure why or what did it but the reason I couldn't delete it seemed to be that the remaining files were locked. Unlocking software didn't show them as locked but they certainly were as no matter how many times I opened the properties and unchecked the read-only box it would not save that way.

I don't think the problem has anything to do with where the Default User folder is saved. I've been having this problem with files in many of our user profiles on our server this past month. I have not been able to find a reason for it nor a solution to it and finally had create a new profiles folder and recreate all our roaming profiles by hand (creating the user profiles folders myself and assigning permissions rather than AD creating them by just specifying the profile path and letting it create the folders/assign permissions if they didn't already exist) to fix it because users would get errors on log on/off and it wouldn't load their profile. I had another post about that somewhere here.

Obviously I'm not a network administrator (I'm a PC tech). I work for a private school with a very limited budget, and since I'm the only technically inclined person there, and I work for cheap (I'm a volunteer who gets "paid" in tuition for my kids ~$8400/year) the lot of managing our server fell to me. It's me and Windows 2003 Server for Dummies (and a couple other books).

Report •

Ask Question