account errors when loggin on to server.

I have several servers that are accessed by terminal services. These users were using a single logon until last week. We addded multiple new accounts so they could logon with unique accounts. The problem is when the logon they get two errors and 1 error when they logoff. The first one states "windows cannot copy file ....pds" the second is "windows cannot load the profile and is logging you on with a temporary profile..." the last is "windows cannot update your roaming profile.." (we don't use roaming profiles).
At first I thought it was permissions issue. Checked and they are ok (I think). I also increased the virtual memory adn applied the MS patch (UPHCLEAN).
All of these throw the event log Userenv 1000 (application).
I've checked the accounts and even moved a couple to the plain Users folder. No change. Any of the administrative accounts logon just fine.
This seems to be a nuisance more than anything else but to the user they see the error and worry.
What else can I try?
gaskewAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Casca1Commented:
Granting Terminal services access based on group membership, rather than local users. The permissions for local accounts has to be manually added to each resource you want the user to have access to; Remember, the user logs in as the term user, and unless you have matched group membership and folder security permissions exactly, your users will have errors.
The error you are having is specific to the way terminal services logs on a user. I think you have the profiles set to load their user drive, and mappings. If that's the case, the local profile can't be created because the user has no access to their normal home shares.
If you go into the term server settings for connections on the terminal services server, you can right click and set global properties. It sounds as if you might have some settings in there that are causing the issue. Either that, or a script you run at logon.
Good Luck!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gaskewAuthor Commented:
I went into TS connections (rdp) and checked the settings. User drive mapping is disabled.We are not running a logon script. This started happening when a person made up a bunch of new t.s. accounts. Would copying new accounts cause any of this?
0
gaskewAuthor Commented:
found out that it was a permission issue! I looked at the sis.sps.pds file and noticed the ts group was not included. This took care of the first two errors. Now if I could only get rid of the roaming profile error when they logoff....
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.