Welcome to Dirteam.com/ActiveDir.org Blogs Sign in | Join | Help

Matt Johnson's Technical Adventures

One server at a time.
The Last Hope Talks Released

If you are like me and didn’t get the chance to go to The Last Hope (The conference put on by 2600 Magazine.), you can now download the talks in .MP3 format.


I am a huge fan of 2600 and have been reading it for years. I hope to go to the conference next time it is offered.

Interesting Links – 7/31/2008

Random PowerShell Cmdlet Fun

I wanted to see what additional PowerShell cmdlet’s I had installed on my computer. I found out that get-pssnapin does the job!

Just run the following in your PowerShell window:

get-pssnapin –registered

You should get an out put like this:

PS C:\tools> get-pssnapin –registered

Name        : Quest.ActiveRoles.ADManagement
PSVersion   : 1.0
Description : Registers the CmdLets and Providers in this assembly

PS C:\tools>

Then all you do to load the snap in is type:

add-pssnapin Quest.ActiveRoles.ADManagement

If you wanted to load all available snap ins, just type:

get-pssnapin –registered | add-pssnapin

PowerShell gets better by the day.

Interesting Links – 7/25/2008

Interesting Links – 7/16/2007

Interesting Links 7/09/2007

The list is a little longer today because of not posting last week. Enjoy!

Interesting Links – 6/24/2008
Interesting Links - 6/18/2008
Interesting Links – 6/11/2008

This week’s interesting collection of links!

Exchange 2007 Command Fun: Update-OfflineAddressBook

Everyone that manages email has most likely run into the following problem once before.

Someone has requested that you create a group so everyone can email them for a specific project that they are working on. You create the group and say “You’re all set”. They go to select the new group from the address list and the group isn’t there. Duh, you forgot to update the offline address list.

There are two ways you can do this, one is using the MMC and the other is using PowerShell. Now I have made it my goal to completely manage Exchange 2007 from the command line. I used to do everything else from the command line, but I was still going to the MMC to update the Offline Address Lists. So today I got sick of waiting for the MMC, so I looked up the cmdlet and found out it was quite simple.

The command that you want is Update-OfflineAddressBook. Now how simple is that. Here are some usage examples:

Update-OfflineAddressBook –Identity “Default Offline Address Book”
Update-OfflineAddressBook –Identity “California Address Book” –DomainController “ca.testing.com”


Interesting Links - 6/3/2008

This week's collection of interesting links!

Deploying Legal Notices via Group Policy

Mike from the Active Directory Services Team has posted a good article about deploying Legal Notices and keeping the formatting.

You can read it here.

Microsoft SharePoint Capacity Planning Tool Released!

Microsoft released the SharePoint Capacity Planning tool. This is an update for System Center Capacity Planning Tool. SSCP 2007 already supported Exchange 2007 and it lets you export the topology to Visio or hardware configuration to Excel. It also allows you to model server performance and end-user response time.

The SharePoint tool gives you the same information except it's information is related to SharePoint.

You need to have SSCP 2007 installed to use the SharePoint Capacity Planning tool.

Information Links

Download Links


White Paper: Configuring Virtual Organizations and Address List Segregation in Exchange 2007

This seems quite interesting when you have multiple companies using the same Exchange server. 

View the White Paper here


This white paper provides the information that you need in order to configure Microsoft Exchange Server 2007 with multiple address lists so different groups of users can have their own address list and secure those address lists so that groups of users can only see their specific address list.

Much of the information in this white paper originally appeared as individual Help topics in the Exchange Server 2007 Help. In this white paper, we have consolidated the information that you need to deploy and manage segregated address lists in one central location. We have also provided sample scripts, which can be modified to fit your environment, to help automate the provisioning of virtual organizations and users.

Moving WSS 3.0 Databases
While building a Windows SharePoint Services 3.0 server, you can't specify the location of the Microsoft SQL Embedded Edition (MSEE) databases. As any good admin would do, I wanted to separate my data from my system files. So I set out to move the databases that SharePoint uses. Here is the step by step I used to move them.
  1. Download and install the Microsoft SQL Server Native Client and Microsoft SQL Server 2005 Command Line Query Utility from here.
  2. Open up services.msc and stop the following services:
    • Windows SharePoint Services Administration
    • Windows SharePoint Services Search
    • Windows SharePoint Services Timer
    • Windows SharePoint Services Tracing
    • Windows SharePoint Services VSS Writer
  3. Open a command prompt and go to the following location:
    • C:\Program Files\Microsoft SQL Server\90\Tools\binn
  4. Enter the following command
  5. To get the list of your SharePoint databases enter the following commands
    • select name from sys.databases
    • go
  6. You can now move any of the databases that start with SharePoint_ or with WSS_. You start moving the databases by typing the following command to detach the database:
    • exec sp_detach_db "<sharepoint_database_name>"
    • go
  7. Open up Windows Explorer and browse to the following location:
    • %SystemRoot%\sysmsi\ssee\mssql.2005\mssql\Data
  8. Copy both the .mdf and .ldf files for the database you just detached from SQL to your desired location.
  9. Now attach the database by entering the following command at the command prompt.
    • exec sp_attach_db @dbname = N'<Database_Name>', @filename1 = N'<New_Location>\<Database_Name>.mdf', @filename2 = N'<New_Location>\<Database_Name>_Log.ldf'
    • go
  10. Repeat steps 6 through 9 for each database you want to move.
  11. Type Exit to close the SQL Command Line Utility.
  12. Start the following services:
    • Windows SharePoint Services Administration
    • Windows SharePoint Services Search
    • Windows SharePoint Services Timer
    • Windows SharePoint Services Tracing
    • Windows SharePoint Services VSS Writer
  13. Verify you can now access your SharePoint sites.