Guest Erik Kristoffersen Posted September 25, 2008 Posted September 25, 2008 At the local school I have got the following problem with a brand new installation af Windows 2008 TS: Suddenly every session is halted when accessing the file server. When the problem arises, client sessions may be able to continue working, however when they access the file server, they will be halted. Problem can be cured by restarting the file server (which by the way is fully functional). Setup: HP ML350 G5p, 4 GB RAM, 2 x 146 GB HD is running Windows 2008 x64 (terminal server) HP DL320 G5, 4 GB RAM, 4 x 250 GB HD is running Windows 2008 x64 (domain controller, file server, TS license server etc.) Home folders stored on the file server, redirected My documents etc. to home folder share All users are sharing the same login. I suspect the problem might be caused by all users sharing the same login and thus accessing the same homefolder. But I would think that this is a supported scenario. So could anyone shed some light over why this is happening? Thanks in advance Erik
Guest Jeff Pitsch Posted September 25, 2008 Posted September 25, 2008 Re: Windows 2008 TS locking problem Actually sharing a single account like that is not really supported at all. Profiles, locking, etc are not designed for that type of scenario (especially profiles). Try using separate accounts and see if the problem persists. Jeff Pitsch Microsoft MVP - Terminal Services Erik Kristoffersen wrote: > At the local school I have got the following problem with a brand new > installation af Windows 2008 TS: Suddenly every session is halted when > accessing the file server. When the problem arises, client sessions may be > able to continue working, however when they access the file server, they > will be halted. Problem can be cured by restarting the file server (which by > the way is fully functional). > > Setup: > HP ML350 G5p, 4 GB RAM, 2 x 146 GB HD is running Windows 2008 x64 > (terminal server) > HP DL320 G5, 4 GB RAM, 4 x 250 GB HD is running Windows 2008 x64 (domain > controller, file server, TS license server etc.) > Home folders stored on the file server, redirected My documents etc. to > home folder share > All users are sharing the same login. > > I suspect the problem might be caused by all users sharing the same login > and thus accessing the same homefolder. But I would think that this is a > supported scenario. So could anyone shed some light over why this is > happening? > > Thanks in advance > Erik > >
Guest Erik Kristoffersen Posted September 26, 2008 Posted September 26, 2008 Re: Windows 2008 TS locking problem Thank you for your advice. That was the conclusion I had reached myself, but it certainly is valuable to get a second opinion. Erik "Jeff Pitsch" <jeff.pitsch.fake@jeffpitschconsulting.com> wrote in message news:u2uVGQ0HJHA.3960@TK2MSFTNGP04.phx.gbl... > Actually sharing a single account like that is not really supported at > all. Profiles, locking, etc are not designed for that type of scenario > (especially profiles). Try using separate accounts and see if the problem > persists. > > Jeff Pitsch > Microsoft MVP - Terminal Services > > Erik Kristoffersen wrote: >> At the local school I have got the following problem with a brand new >> installation af Windows 2008 TS: Suddenly every session is halted when >> accessing the file server. When the problem arises, client sessions may >> be able to continue working, however when they access the file server, >> they will be halted. Problem can be cured by restarting the file server >> (which by the way is fully functional). >> >> Setup: >> HP ML350 G5p, 4 GB RAM, 2 x 146 GB HD is running Windows 2008 x64 >> (terminal server) >> HP DL320 G5, 4 GB RAM, 4 x 250 GB HD is running Windows 2008 x64 >> (domain controller, file server, TS license server etc.) >> Home folders stored on the file server, redirected My documents etc. to >> home folder share >> All users are sharing the same login. >> >> I suspect the problem might be caused by all users sharing the same login >> and thus accessing the same homefolder. But I would think that this is a >> supported scenario. So could anyone shed some light over why this is >> happening? >> >> Thanks in advance >> Erik >>
Recommended Posts