Since the release of Vista, you can use the command line utility slmgr for Windows activation when using a MAK (or Multiple Activation Key).

Windows Activation

1. Open a command window (as administrator)
2. And run…

slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
slmgr -ato

Office Activation

1. Open a command window (as administrator)
2. From C:\Program Files\Microsoft Office\Office14 run…

cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
cscript ospp.vbs /act

Who needs all that pointing and clicking anyway?

Over the past few months I’ve been pointed to, or found, four more sites chock full of tasty utilities.

• AnalogX has a varied collection covering network, system, programming, even audio utilities.
• joeware has a whole pile of free tools, many related to Active Directory, account management and networking.
• NirSoft has an impressive array of tools for forensics, networking, systems, passwords and a whole lot more. They also have a blog so you can keep posted on updates and additions.
• Optimum X has a decent list of network, software and login utilities. Although some are a bit long in the tooth (one is from 9/98), there’s still some gold here.

These should keep you busy for at least a few minutes. And as always they’re my favorite price, free.

To confirm that this was the case, I opened the trusty EMS and ran this command on an affected individual.

test-exchangesearch username | fl

This result confirmed the catalog corruption:
ResultFound : False
SearchTime : -1

The fix is rather easy, but depending on your database size, can be rather lengthy. The script below stops the Microsoft Exchange Search Indexer, deletes the Catalog of the database in question and restarts the Indexer which fires off a complete rebuild.

You can find the script here (from where it must be run): <drive>:\Program Files\Microsoft\Exchange Server\Scripts

Syntax: ResetSearchIndex.ps1 -force <database>

Example: ResetSearchIndex.ps1 -force “Mailbox One“

The rebuilding of our catalogs took almost an hour for a 80GB database. And that was on a fairly powerful system with 32GB of RAM.

Should you wish to give the script below a try, copy it into a text file and change the extension to .ps1

Note: This script should be run from a system with Outlook and the Exchange Management Tools installed (they both need to be 32 or 64-bit) for this to work).

rem Gathering names for labeling the exported PST
$fname = Read-Host “First name?”
$lname = Read-Host “Last name?”

rem Assigning the current date to the $date variable
$date = get-date -uformat “%Y_%m_%d”

rem Capturing name of mailbox account (assigning to $uname variable)
$uname = Read-Host “Username?”

rem Capturing admin acct that is currently logged in to add mailbox permissions (assigning to $admin variable)
whoami > $admin

rem Adding permissions for admin allowing export
Add-MailboxPermission -AccessRights FullAccess -Identity $uname -User $admin

rem Exporting mailbox to D:\PSTs (change path to your liking)
Export-Mailbox -Identity $uname -PSTFolderPath D:\PSTs\$fname”_”$lname”_”$date.pst

If at some point I get time or get paid to do so, I’ll make a script to allow the use of a list for mass export.

Little did I know someone changed the top-level permissions of the folder I previously created, removing any admins from the list, so any new folder in the tree inherited the lack of admin rights. Now I had to change permissions on 472 folders, not something to be done individually.

A short search yielded just the info I needed. There is a script called AddUsersToPFRecursive.ps1 in the \Microsoft\Exchange Server\Mailbox\Scripts directory; use and syntax is below.

AddUsersToPFRecursive.ps1 -toppublicfolder \Finance -User “Joe Admin” -Permissions Owner -Confirm:$False

Change the -toppublicfolder to \ or \Marketing\Calendars, whatever suits your needs. And be sure to add the -Confirm:$False switch, otherwise you will have to hit Enter (or Yes) for every folder change. Don’t ask me how I know…

Whenever you try to run an unsigned PowerShell script, you get the following message: “File C:\Custom\Test.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details.”

I certainly believe Microsoft is doing the right thing with keeping PowerShell script execution secure with the proliferation of malware and 99%+ of Windows users don’t even know about PowerShell.

Changing the PowerShell security setting is a simple affair. Open PowerShell as an Administrator and run the following: Set-ExecutionPolicy

Your choices are:
Restricted (default) – Which stops all unsigned scripts from running.
AllSigned – This allows only signed scripts to run.
RemoteSigned (my recommendation) – Allows local scripts to run, but all downloaded or remotely executed must be signed.
Unrestricted (not recommended) – This allows all scripts to execute, whether from an e-mail, website or instant message.

Syntax: Set-ExecutionPolicy RemoteSigned

Just replace the text in bold red and run it in an Exchange Command Shell:

Set-MailboxAutoReplyConfiguration jsmith@contoso.com –AutoReplyState Scheduled –StartTime “11/2/2011” –EndTime “11/9/2011” –ExternalMessage “External OOF message” –InternalMessage “Internal OOF message”

It’s a very nice alternative to the built-in feature in Windows Server 2008 R2 and is a drastic improvement over item recovery in earlier versions of Active Directory with a great GUI interface.

They have a couple of other interesting products in Maven, ResetPass and Action Engine, not everything is free, but it’s close.

Sysinternals started as the community or free arm of Winternals, the money making portion of the company. Microsoft purchased Winternals back in 2006 for its IP and brain-trust. Mark Russinovich has been the most active of the original staff, appearing at numerous conferences, blogging and evangelising the Microsoft operating systems.

The Sysinternals site has numerous, extremely useful troubleshooting and informational utilities; so much so I could devote this blog to their tools for the next year or three. Since access to the site is free, as are the downloads, help files and instructions, I’ll just highlight a few things here…

Utilities:
Autoruns – Displays list of applications, drivers loaded and much more, that start at boot time. Includes locations of registry and file locations. Great for hunting malware.
Process Explorer – Displays all running processes and subprocesses, plus open handles, threads, paths, a veritable cornucopia of information. Task manager wishes it was this great.
Process Monitor – Allows you to monitor file system, registry, process, thread and DLL activity in real-time.
TCPView – Get detailed listings of all TCP and UDP endpoints on your system, including source and destination.

The Learning Resources are also impressive, with great videos and articles .

And as I mentioned, this is all free.

From a command line or in a script wmic bios get serialnumber will display or grab the Dell Service Tag.

Furthermore, you can use the WMI Command-line to retrieve all kinds of system data and even make configuration changes. Rob van der Woude‘s great site on scripting has a great primer and examples on using WMIC. TechNet Magazine also has a very useful article on gathering system data using WMIC in your environment.

Finally, checkout the WMI Admin Tools pack. It contains more than I want to type about here, but it gives you the ability to browse the various objects, classes and properties, plus a custom event viewer and much more. Check it out and make your (administrative) life better.