plock

Fair enough, I thought I was a geek!

I have setup similar scenarios previously, I have used a batch script to add %username% to the Local Administrators Group on the machine. This was run in a Startup Script; I’ve also added it into the same GPO that has the modified GUI permissions. Then moving the laptops into another OU, or modifying the existing one, change the Group Policy to not block the Control Panel applets required and so forth. As stated above, Group Policy will override the Local Admin Privileges. Now to attend to a fire alarm!!

The Dell XP CD's are slipstreamed, similar to a Sysprep'd image. Making the correct modifications to the 'Sysprep.inf' answer file will allow this process to be automated in the final Sysprep'd image. The following article may help you automate the process: http://support.microsoft.com/kb/302577 Good luck!

Nor CD ROM at this rate!

Fair enough, perhaps IE7 Pro Addon then.

IE7 Pro isn't bad, if I remember rightly they've added a Spell Checker. http://www.ie7pro.com/ Other than that, check your own spelling!

There are various sites that have spell checking facilities, such as http://www.spellcheck.net. Why not use something like Word, or as Geoff does, use a browser with spell checking built in. BTW, what browser do you use?

I would suggest changing the NTFS permissions accordingly, NTFS will restrict the files/folders to individuals or security groups defined on the 'Security' tab.

I've come across a couple of applications that can do this, no scripts as such though. http://desktopengineer.com/story_2001043008283895 http://www.hainsoft.com/en/download.htm Hope that helps!

It's looking rather funky!

This is very easy to do, Windows NT/2000/XP includes a feature that allows you to configure the computer to automatically logon to the network, bypassing the Win Logon dialog box. To enable this function you need to add several new values to the key below. Add a new string value named 'DefaultUserName' and set it to the username you wish to automatically logon as. Add a new string value named 'DefaultPassword' and set this to the password for the user entered above. Add a new string value named 'DefaultDomainName' and set this to the domain of the user. Add a new string value named 'AutoAdminLogon' and set it to either '1' to enable auto logon or '0' to disable it. For Windows 2000 the additional ForceAutoLogon setting must be enabled to stop the tweak from resetting on reboot. Exit and restart, Windows should not ask for a password and automatically show the desktop of the user. Note: The password is stored in registry, which means anyone who has access to the machine has access to the password. Note: You can bypass this function by holding down the SHIFT key during the boot or logoff process. Note: It is also important to note that if the DontDisplayLastUserName value is enabled, the auto logon feature does not function. Registry Settings: System Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] Value Name: AutoAdminLogon Data Type: REG_SZ (String Value) Value Data: (0=disable, 1=enable) Good luck!

You then need to go from the server to the exchange site. Try using: https://servername/exchange. Or whatever you called your 'Outlook Web Access' site in IIS. Hope that helps!

Currently finishing up installing our new computer suite (30 machines); a whole load left on the to-do-list though!

IT Support here...

You're welcome! Glad to hear you're back up and running!

IT or Science Teacher was it? hehe

Also, perhaps a corrupt message in the information store is causing this. Perhaps try ESEUTIL to check integrity and repair the problem. Here are some support articles to help: http://support.microsoft.com/default.aspx?scid=kb;EN-US;182903 http://support.microsoft.com/default.aspx?scid=kb;en-us;301460&Product=exch2003 I also picked this up a second ago, it may help: This issue is mostly related to the antivirus application running on the server. I suggest you disable all the third-party tools, especially the antivirus applications, and then try to manually perform the backup process. Also, please check if there are third-party e-mail disclaimer applications installed on the server, which may also cause this issue. For more information, refer to the following article: http://support.microsoft.com/?id=840013 If the issue persists, please check if the Exchange database is correct using the following: 1. Run eseutil /g to test if the status of Exchange databases is OK. 2. Run Isinteg -fix -test -alltests again to verify there is no error/warning. In addition, we suggest you configure the antivirus software excluding the following items from being scanned: - Exchange databases and log files. - Exchange .mta files (default location: \Exchsrvr\Mtadata). - Exchange message tracking log files (default location: \Exchsrvr\.log). - Virtual server folders (default location: \Exchsrvr\Mailroot). - Site Replication Service (SRS) files (default location: \Exchsrvr\Srsdata). - Internet Information Service (IIS) system files (default location: \%SystemRoot%\System32\Inetsrv). - Internet Mail Connector files (default location: \Exchsrvr\IMCData). - The working folder that is used to store streaming temporary files that are used for message conversion. By default, this working folder is located at \Exchsrvr\MDBData. - A temporary folder that is used in conjunction with offline maintenance utilities such as Eseutil.exe. By default, this folder is the location that you run the .exe files from, but you can configure this when you run the utility. More info here: http://support.microsoft.com/?id=245822 Now, finally, hopefully somewhere amongst this you’ll find the answer! Good Luck!

A quick search picked up this: http://groups.google.co.uk/group/microsoft.public.windows.server.sbs/browse_thread/thread/d5e5ceba8b4ff45b/d93572ea352c58a8?lnk=st&q=%27The+%27Microsoft+Information+Store%27+returned+%27A+disk+I%2FO+error+occurred.%27+&rnum=1&hl=en#d93572ea352c58a8 I'm not saying this will cure the issue at all, but perhaps take into account what else is happening around that time. The above posts don't give an answer, nor do they even say if changing the backup time worked; but never the less, maybe give that ago?

I have had issue previously with backing up Exchange. However, my errors were not directly the same as your errors. The issue was due to inactive Mailboxes on the system. Purging the Mailboxes fixed the issue. Hope that helps.

To get last logon information we have placed a command in the login script to write to a text file with the following variables, %username$, %time% and %date%. This is then outputted to two different files, one named with the computer name and the other named by the username. This is so we can track computer and user usage.

Mandy Brereton [OLIIS] - [email protected] Give her a shout; let her know Paul/Trevor from John Madejski Academy give you their company as a recommendation. I'm sure she'll be able to help you. They're also very good a price matching!

Cheers, saved me doing the testing!!

I've not managed to have is run on the login screen; I feel this is because it's collecting account information on login. I've not researched extensively; I was going to give putting it in the startup script ago to see what happens.

We had no issues, I completed it at the end of last week!

CSVDE also works for us!