Recent content by GuyThomas

I suggest a new script for the new operating system. Replace .bat with .vbs. Then assign scripts via policies rather than throught the individual user's property tab.

There are registry editing policies. Disable: Prevent access to registry editing tools Watch out for the double negative. In Group Policy, Navigate to the User Configuration Windows Component System

What you need to do is a) Plan what you want the scripts to do e.g. Map Network Drives Map printers. Then copy an existing VBScript, change the names of the shares and printers and try it out. Assign your scripts via a Group Policy, rather than the individual's property box (avoid NT way)...

Firstly, I would make sure you backup the system state What you are looking for is a checkbox when you make a backup using Microsofts builtin program in the Accessories, System Tools. Here is more information on what the System State backup will do for you...

I have had success with the USMT user setting migration tool This neatly packages all the user files, then you unpackage them when the move is complete. http://www.computerperformance.co.uk/w2k3/W2K3_ADMT.htm Guy Thomas Scripting Ezine...

What about creating a new policy at the DOMAIN level - naturally. Make it as viscious as you like, but set the security such that it only applies to the one machine. Remove Authenticated Users, and just add the computer name to that policy. (Make sure your View, Advanced, then use the...

Once you have Windows 2003 installed, seek out the Active Directory Migration Tool. ADMT. See more here http://www.computerperformance.co.uk/w2k3/W2K3_ADMT.htm As for the migration, I always have found it best to go for a clean new domain and create the users via scripts. However there may be...

You need lots of planning with an upgrade from NT to W2K3. The old saying is 7 mins of planning will save an hour of rework. Firstly will you need a period of co-existence between the old and the new domains? Following on from this,next queston will you create new accounts in the new domain...

You need lots of planning with an upgrade from NT to W2K3. The old saying is 7 mins of planning will save an hour of rework. Firstly will you need a period of co-existence between the old and the new domains? Following on from this,next queston will you create new accounts in the new domain...

There is a group policy setting which controls the IE Proxy server. My only misgiving is does only work on XP W2K3. The setting is Under the User Config Windows Settings Ie Browser User interface. See more here...

May ask if the script executes on its own? If no what error messages does it produce. If yes then are the users in the ou where you run it? Which client do you use. If Win98 assign via user properties. Guy Thomas Scripting Ezine http://computerperformance.co.uk/ezine/newsletter_subs.htm

Native mode would only affect BDCs in the same domain, so I cannot see any problems. In any event you could still create trusts whether or not they were NT or W2K domains. Guy Thomas Scripting Ezine http://computerperformance.co.uk/ezine/newsletter_subs.htm

I am with Robert. VBScript it the way to go. Dare I say that Assigning VBScripts via group policies is the way of the future. User Property pages and batch files are the way of the past. That said, creating Logon VBScripts is not that hard, my guess is that people just copy existing scripts...

Try a group Policy Computer Configuration Administrative Templates System Logon Always use classic logon For more interesting Group Policies see here: http://computerperformance.co.uk/w2k3/W2K3_group_policy.htm Guy Thomas Scripting Ezine...

Windows 2003 DC should behave just like any other server. There is the Raise Domain and Raise Forest level concepts that replace the Mixed and Native mode. Here is more information on Raising the levels http://computerperformance.co.uk/w2k3/w2k3_mixedvnative.htm Guy Thomas Scripting Ezine...