HELP - Windows 2003 SBS and 2003 Terminal Server
Discussion
Hi All,
I am installing two new servers over the weekend set up as 1x 2003 SBS and 1x 2003 Terminal server. We are moving from 1x 2000 Server Standard running as PDC and Terminal Server.
The problem I?ve got is we set-up a Group Policy to lock down all the users (which works a treat and strangely reduced support calls by 90%!..) - anyway the problem is as follows;
I've created the new Group Policy on the SBS server which works fine with the exception on folder redirection. I've set up a My Documents redirect within the group policy to a UNC path on the SBS server however when testing with a user account it hasn't redirected?! Anyone have any thoughts?
Thanks in advance...
I am installing two new servers over the weekend set up as 1x 2003 SBS and 1x 2003 Terminal server. We are moving from 1x 2000 Server Standard running as PDC and Terminal Server.
The problem I?ve got is we set-up a Group Policy to lock down all the users (which works a treat and strangely reduced support calls by 90%!..) - anyway the problem is as follows;
I've created the new Group Policy on the SBS server which works fine with the exception on folder redirection. I've set up a My Documents redirect within the group policy to a UNC path on the SBS server however when testing with a user account it hasn't redirected?! Anyone have any thoughts?
Thanks in advance...
Permissions on the share?
First, check you can actually connect to the share when logged in as the user and read/write files... Check security on the shared directory too.
Not related, but a tip worth remembering.
Never ever under any circumstances store a roaming profile in the users home directory!!!!!
First, check you can actually connect to the share when logged in as the user and read/write files... Check security on the shared directory too.
Not related, but a tip worth remembering.
Never ever under any circumstances store a roaming profile in the users home directory!!!!!
I did this earlier this week!
I had to remove and recreate all the users using the "User Template" to get it to work.
Either that or load each profile and change it manually before dorpping them out of the admin group...
Mail me with any other issues as I'm just working through a few myself.
I had to remove and recreate all the users using the "User Template" to get it to work.
Either that or load each profile and change it manually before dorpping them out of the admin group...
Mail me with any other issues as I'm just working through a few myself.
MickC said:
Why not?
Err, It will delete all their files!
Let's just say I know from bitter personal experience. Quite scary to watch a whole classroom full of kids losing their work as they log off!!!
Details here
http://support.microsoft.com/default.aspx?scid=kb;en-us;182079
Bit of a cock up, not mentioned in that doc, but basically it does a delete and an xcopy. Big whoops from MS
BliarOut said:
BliarOut said:
Why not?
Err, It will delete all their files!
Let's just say I know from bitter personal experience. Quite scary to watch a whole classroom full of kids losing their work as they log off!!!
Details here
http://support.microsoft.com/default.aspx?scid=kb;en-us;182079
Bit of a cock up, not mentioned in that doc, but basically it does a delete and an xcopy. Big whoops from MS
Oh I see what you mean. No, don't make the profile folder and home folder the same, that would be asking for trouble. 
But you can store the user profile in a folder within the users home directory. In fact that's the best place to put it.
It gets even better when users start putting files on their desktop on WTS, especially big files. Best to prohibit that. Otherwise the profile takes ages to copy down. And desktop files can easily get lost if the profile server is not available and a new local profile is created, as the 'new' profile just overwrites the existing one (and deletes all the files from the desktop folder).
Roaming profiles and WTS. We love em.
Roaming profiles full stop.
Biggest nightmare of all. Please please MS, give me an option to say thanks, but no thanks.
Bloody bastard things, I hate them.
Six hours to transfer four profiles the other day because I added the first server to a company network and they wanted to keep the existing ones with all their buried OE mail etc. It only took an hour to prep the whole server FFS.
Oi, Microsoft, NO!
Biggest nightmare of all. Please please MS, give me an option to say thanks, but no thanks.
Bloody bastard things, I hate them.
Six hours to transfer four profiles the other day because I added the first server to a company network and they wanted to keep the existing ones with all their buried OE mail etc. It only took an hour to prep the whole server FFS.
Oi, Microsoft, NO!
BliarOut said:
Roaming profiles full stop.
Roaming profile disaster stories? OK then
Some users decided they wanted roaming profiles, because they often moved around the office with several different machines. OK, say the helpdesk, and create roaming profiles for the whole site.
So, next time the user logs on, no roaming profile. No problem, it uses the local one. Then when they log off, it copies the local one (inc 'My Documents'
) up to the server. They log on somewhere else. The now roaming profile from the last machine is pulled down from the server, overwriting the local one on that machine. 'WHERES MY DATA GONE!', says the user, who's stored different data on each machine. Oh dear. Even better, the Server disk fills up PDQ, with all this data pulled from the local machines. Can't copy the whole profile up to the server - next time user logs on, he gets a user.dat and that's all. Oh and btw, any data in the existing cached profile is deleted. Lovely.
Backups? Guess what, local machines are not backed up, that's what your home drive is for. And the profile wasn't on the server long enough for the nightly backup to run. Oh dear.
All I can say is thank God I didn't sign that CC off.
I learned to avoid roaming profiles years ago 
Users get a home share, policies set this as the default save location and the user is told never ever to save in my documents.
Workstations are sacrificial and data lives on the server IMHO.
Even if you implement it perfectly, MS will subtly alter things from time to time and in such a way as to somehow erradicate the profile.
Bought a copy of restorer2000 pro for this very reason.
Why oh why would someone design an OS that intermittently deletes the storage location for your e-mail!
Bloody spawn of satan those profiles.
Users get a home share, policies set this as the default save location and the user is told never ever to save in my documents. Workstations are sacrificial and data lives on the server IMHO.
Even if you implement it perfectly, MS will subtly alter things from time to time and in such a way as to somehow erradicate the profile.
Bought a copy of restorer2000 pro for this very reason.
Why oh why would someone design an OS that intermittently deletes the storage location for your e-mail!
Bloody spawn of satan those profiles. 
HELP!
Done the upgrade and everything working fine but I'm getting a major problem with MS Access 2000.
When users try to print access just closes without an error message. On checking the system logs i'm getting the following;
"Reporting queued error: faulting application MSACCESS.EXE, version 9.0.0.6620, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x0000744e."
Anyone have and ideas? Everything is running the latest updates!...
Done the upgrade and everything working fine but I'm getting a major problem with MS Access 2000.
When users try to print access just closes without an error message. On checking the system logs i'm getting the following;
"Reporting queued error: faulting application MSACCESS.EXE, version 9.0.0.6620, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x0000744e."
Anyone have and ideas? Everything is running the latest updates!...
Whack it in Google and it would seem you're not alone.
I would suggest a visit to www.microsoft.com/technet and post it in the newsgroups there. The Access lot are usually pretty helpful.
I would suggest a visit to www.microsoft.com/technet and post it in the newsgroups there. The Access lot are usually pretty helpful.
Hi
I'm getting all sorts of errors;
"You tried to commit or rollback a transaction without first begining a transaction"
and "DDE Server the memory could not be read"
Both when trying to view / edit or run reports as before. I have also re-intalled office, rebuild the application etc etc
Looks like I may have to try either upgrading the apo to the latest copy of access or taking the terminal server back to windows 2000! can't decide which is more hassle?! Doh...
Thanks - Posted some messages awaiting replies - just testing office 2003 to see if the apps will run without too much messing about?!
If not I'll have to take the Terminal Server back to W2000 !...So much for having this week off, it's times like this that I seriously consider getting out of IT. As usual the client thinks it will take 10 minutes ?!.....
Theres a MST file you need to apply to Access before installatoin on a Terminal Server.
http://support.microsoft.com/default.aspx?scid=kb;en-us;q224313
>> Edited by alunr on Tuesday 21st December 12:39
http://support.microsoft.com/default.aspx?scid=kb;en-us;q224313
>> Edited by alunr on Tuesday 21st December 12:39
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff