auto logon/off

Microsoft Windows 2003 server - 5 users
July 28, 2010 at 20:41:53
Specs: xp sp3, server 2003
Hello everyone. I am new to the forum..so thank you much.
I am not sure if this has been asked before, if it has im sorry.

I am a recently hired IT admin for a computer company, just started IT school and have alot to learn..my company has about 300 computers..and we run a few servers and such. clients are all on xp sp3 for most part.

My question is, i just had to build 30 new computers and move profiles over to new computers...this caused some issues because nobody here likes to logoff or turn off the computers at night..so when i went to logoff profiles they have to sync w server and that takes forever..some peoples profiles are over 7gig of music...
my question is..is there a way i can make a script(new to that area..), log off policy (new to server)..SOMETHING. that will either logoff users daily at say 11pm....and if that don't work at least shut down the pcs....if possible it would evne be nice to have a logon script as well..so computers all logoff at 11pm..then log back onto the default user at say 6am....that way im not congesting server by 300 profiles being pulled at one time.

thanks for the help in advance


See More: auto logon/off

Report •

#1
July 29, 2010 at 10:43:17
So, if I were you and wanted to do this, here is what I'd do.

Setup a scheduled task to run at 11:pm on each system that runs the command:
tsshutdn 30 /powerdown

That command will tell the system to shut down and power off.

For the startup, it's a litte more complicated. First, the BIOS has to support startup timers. If they do, you can set the startup timer to start up at 6:00am.

To get the autologon to work, you need to modify/add some registry keys.
They are all under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

Default User name - set to the username you want logged on
Default Domain Name - set to the domain name you are using for AD
Default Password - Set to the user's password

Also, create an entry called "AutoAdminLogon" as a REG_SZ and set the value to: 1


Report •

#2
August 16, 2010 at 22:23:46
Wow, I see a few issues here, some of which ntengineer has addressed.

With so many computers, have you ever thought of using Folder Redirection? That would be a great starting point to resolving the long logon/logoff issue. If you are using Roaming Profiles, you should probably want to stop unless your users move frequently and again Folder Redirection can help alleviate much of the bulk of the Profile.

Additionally, if your users are downloading a lot of music and/or visiting unauthorized websites during work time (or on company equipment as some business like to say) then you should really look at a few things that can help cut down or eliminate such wastes. For example, excluding the use of some executable filenames (see software restrictions in GP or prevention of executables.) Another simple fix to help stem the flow of visits to unauthorized websites is to statically assign or redirect websites as A Records on your DNS. Doing this will effectively point your users to another place, such as a "This site is Restricted" page that you could provide. If more robust filtering is needed, there is soft/hardware out there that can do much of this for you, but it will cost you where modifying DNS records will not.

I hope this helps a little, at least. You've got multiple issues going on here, so let's take it one at a time.

If it's worth doing, it's worth doing right.


Report •

#3
March 24, 2011 at 05:33:36
LogonExpert supports both automatic logons and logoffs by build-in scheduler

Report •

Related Solutions

#4
March 24, 2011 at 06:01:27
It strike me that you have a huge non-technical issue here. Users storing personal music (images, videos, whatever) on company computers. Apart from the huge potential for copyright abuse, and the potential liability to the company because of this, this is costing the company in the provision of data space and network connectivity.

You need to have a talk with the Management, in particular HR, and agree a data usage policy for your company. Explain to them how much it is costing and the potential for legal action against the company. This has to come from the Management rather than the technicians, and they must be prepared to enforce it. Sort that out and a lot of your other problems will disappear.


Report •

#5
March 24, 2011 at 08:42:47
We had the same issues not only with music but personal pictures. I don't know what you use to backup but we use robocopy. I think you can do the same thing with xcopy but any ways, we only backup files with .xls* .doc* .pdf* .pp* and so on so that only their business files are backed up. This takes a lot less time and disk space. Here is our script not sure if it helps...

echo Backing up local files...
\\10.100.100.7\scripts\robocopy "%userprofile%" "%Destination%\%username%\Daily" *.do* /if *.xl* /if *.pdf /if *.pp* /if *.txt /XD "%userprofile%\AppData" /XD "%userprofile%\local settings" /XD "%userprofile%\Application Data" /s /COPY:DAT /mir /r:1 /w:1 /np /xo /eta >> h:\BackupLog.txt

Our complete code looks like...
__________________________________________

@echo off
::taskkill /im outlook.exe

Set Monthfolder=Monthly\%Date:~-4,4%-%Date:~-10,2%
Set Destination=\\10.100.100.10\backups\userfiles\
if not exist "%Destination%\%username%" call :createdir

Cls

echo Backing up local files...
\\10.100.100.7\scripts\robocopy "%userprofile%" "%Destination%\%username%\Daily" *.do* /if *.xl* /if *.pdf /if *.pp* /if *.txt /XD "%userprofile%\AppData" /XD "%userprofile%\local settings" /XD "%userprofile%\Application Data" /s /COPY:DAT /mir /r:1 /w:1 /np /xo /eta >> h:\BackupLog.txt


echo Backing up Email...
ver | find "Version 5." > nul

If ERRORLEVEL=0 \\10.100.100.7\scripts\robocopy "%userprofile%\local settings\application data\microsoft\outlook" "%Destination%\%username%\%monthfolder%" *.pst* /s /COPY:DAT /mir /r:1 /w:1 /np /xo /eta >> h:\BackupLog.txt

If ERRORLEVEL=1 \\10.100.100.7\scripts\robocopy "%userprofile%\appdata\local\microsoft\outlook" "%Destination%\%username%\%monthfolder%" *.pst* /s /COPY:DAT /mir /r:1 /w:1 /np /xo /eta >> h:\BackupLog.txt
goto :eof

:createdir
md "%Destination%\%username%"
goto :eof

__________________________________________

Note the ">> h:\BackupLog.txt" is to write the log to the users home directory. If you don't have an H: drive you will need to change this.

Note the "ver | find "Version 5." > nul" will determine which OS they are using. We have some Windows 7 boxes and the email is stored in a different directory on those OSs. If errorlevel 0 it is XP otherwise it is VISTA or 7.

The part with the email is a little different because we do not have an Exchange Server (I know old school) so peoples PST files get backed up to a monthly folder so we can retrieve emails they might have deleted from a month ago. (Don't ask users do strange things.) You don't need to use that part of the code if you don't want. If you want to use robocopy you will need to download the Windows Resource Kit unless you have 2008 server then it is included. For 2003 it is a free download...

http://www.microsoft.com/downloads/...

I do agree with the scheduled events for people who do not logoff their computers. Be careful when doing this because if you schedule all of your workstations to backup at the same time you will overload your network and it could take hours to do the backups. You may have to stagger the hours and days so you don't have too many running at the same time.


Report •

Ask Question