Extra88

I thought this was sort of an interesting Microsoft KB article.
OL2000: Preventing Reply All to Large Aliases

In a nutshell the offer 3 methods. The first is simply to use the Bcc: line (duh). The second is the most interesting and clever to me, create a custom Mail Message Form which has no Reply to All button. Recipients could still use other Reply to All methods but it would foil the unconscious hitting of that button because IT WOULDN'T BE THERE! The third is to use a system policy which disables all Reply to All methods in Outlook. If you're the kind of sysadmin who roots for the "bulls" in prison movies, that's the option for you.

This falls under so many categories. MacOSXHints has this storyAn AppleScript to look up NetBIOS names. but Real Men use the Terminal. Here's the command line bit that does the real work:

nmblookup -T -U <WINS server IP> -R <NetBIOS name>

We haven't used Sysprep yet but we probably will. This will impact procedures for using Sysprep.

Opportunistic Locking May Not Be Granted If Windows Is Installed by Using Sysprep

The workaround is to delete the data from this Value after running Sysprep on the master but before shutting it down.

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\lanmanserver\parameters
Value: GUID

This is an interesting script. It has some room for error but I have an idea about how to avoid that.

Some fellow who seems to work for Microsoft in some capacity has written a batch script called MakeMeAdmin that uses runas in clever ways to make a program run as the user but with admin privileges. The advantages over simply running programs using a local admin account are the program will use the user's profile instead of the admin account's and the programs will have access to domain resources.

Here are the phases of the script:
1. Open a command prompt as a local administrator (user is prompted for this account's password)
2. Current user is added to the local Admin group
3. Open command prompt (or another specific program) as current user (user is prompted for their own password)
4. Current user is removed from the local Admin group

Changes to group membership don't affect existing login sessions, only new ones. Therefore when runas is used in step 3 to start a program as the current user, it's a separate session and therefore the Admin group membership takes affect. Step 4 can happen immediately because the user's removal from the Admin group won't affect the session opened in step 3.