• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 249
  • Last Modified:

User Profiles

I am confused by different people on user profiles.

We are on Windows Server 2008 R2 Enterprise and run 2 terminal servers for branch access.

On the terminal servers??   I see under my C: drive - Document and Settings and then there is the entire list of my users including one called All Users
On the C: drive I also see a folder for Users and again there is the entire list of my users, and a folder called Public

Ok...here is where I get more confused.

C:\Documents and Settings\All Users---There is Desktop.  I look in that folder and the desktop icons that ALL my user need are there.

Then I go to C:\Users\PUBLIC ---  There is Public Desktop and again all the icons (shortcuts) are showing there.

Which path should I be using when I need to add a new shortcut for all my users?

The ALL USER folder or the PUBLIC folder
  • 2
1 Solution
Jason WatkinsIT Project LeaderCommented:
It sounds as if the "All Users" folder is the default profile for the T/S users and the "Public" folder is for items that can be accessed and shared to everyone who uses the computer. A shortcut placed in Public would affect all users of the computer, whereas the same shortcut placed in All Users might only apply to new profiles created on the system.
bankwestCTO/CashierAuthor Commented:
Thank you for clearing that up for me.    Sometimes the simplest things can cause a major headache.   LOL
Jason WatkinsIT Project LeaderCommented:
Thanks for the points
David Johnson, CD, MVPOwnerCommented:
the real answer is that 'Documents and Settings' is a a link to c:\users used for backward compatibility . it doesn't really exist.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now