Local User vs Default User 3

[Questy]

I am testing and configuring Zen Works. I am trying to better understand the differences between when something goes in the Local User vs Default User folder. After scanning through the 1700 pages of Microsoft's Windows 2000 Professional Resource Kit, and searching Microsoft's website, I can't say I've learned much about this issue.

Any insight, or resources you could point me to for futher learning would be appreciated.

 

[butchrecon]

Someone correct me if I am wrong, but I believe "local user" is used to describe a specific user logged on locally. "default user" is used to describe the default settings for users. I am not sure on this. I could be way off base.

Any one else have any input?

 

[Questy]

Scenario: You are logged on to NT (W2K) as administrator and load an application so that all users who are created on this workstation can use the application.

Why is there a folder called All Users, and one called Default user? What is the difference???

My goal, (I think???) is to be able to load software, or make changes, to the default user. This way all dynamic users, (through ZenWorks), have these applications available as they "inherit" the default profile.

 

[mcconmw]

All Users gets used by all users every time. Default user is the template that user settings are copied from the first time a user logs on.

 

[Questy]

I've done a bit of experimenting with this today. While I've come up with a work around, I still haven't found the answer to the how's and why's of the default user.

- I started with a "clean" W2K workstation image. Logged on to the workstation only as administrator, and loaded some software such as MS Office, and my e-mail client, (GroupWise). Configured the e-mail client, (which is basically just entering the IP of the post office), and the browser, (added the proxy info). None of the config information got saved to the default user, it was saved to the administrator's profile.

- Once I had everything configured the way I wanted it, I then copied the administrator's profile to the default profile.

While this solves my problem, it still doesn't make sense to me. Is this normal? You can't "install" anything to the default profile?

 

[mcconmw]

Typically installs would not go to the default user since the primary purpose of profiles is to allow individual customization. The solution you have found is the standard way to alter the "customization" of the default user. When a user logs on to a pc for the first time the default user profile is copied and renamed to the username of the person that is logging on. After the profile is copied, the only way to alter every user to the workstation is to make changes to the All Users profile. Basically, if you want something available to everyone on a specific machine you should alter the All Users profile, because it will affect all users old and new. Changing Default Users will only affect new users to the workstation. If this explanation doesn't help, let me know. My email is mcconmw@hpd.abbott.com and I will be happy to discuss this further.

 

[dsturgeon]

Create a user called temp and give this user admin rights. Then log in as this user and do your install. Then log back in as admin and copy the profile over to the default user, giving 'everyone' rights to the profile.

If you install a program using your 'default' user (temp), and make all your config changes and customizations, they should carry over to your new default profile once copied.

 

[Questy]

I was getting rather frustrated by the fact that information on profiles was not well documented by MS. Then again it brought back memories of profile issues encountered when we first started using Win95.

Thanks to you both for your input. It's all making sense to me now.