Archive for the ‘Tech’ category


Registry Checking Binary Values With Labtech Scripting

When performing a binary value registry check with the equals comparator you may notice that your check isn’t returning a success when it should be. There’s a gotcha you should be aware of that’s present in atleast Labtech 2013.1 as illustrated below.

Let’s say you’re looking for the following binary value to be present (in hex): 00,00,0F,4E,00

If you perform the registry check in Labtech scripting with that specific value, it will not return a success if the value matches. The reason for this is due to Labtech stripping the leading zeroes in the hex values when it pulls it from the registry.

To search for a binary value you simply need to strip the leading zeroes in your registry check. The correct representation of the above example would be: 0,0,F,4E,0


Stop Exchange 2010 From Changing Resource Calendar Subject Lines

If you’re using resource mailboxes in Exchange 2010 and have it automatically process meeting invites, then you may notice that the subject lines are getting stripped and replaced with the organizer’s name. Depending on how you are using the resource mailbox, this may be an undesired action. If you wish to leave the original subject in the calendar entry, run the following command in the Exchange Management Shell:

Set-CalendarProcessing -Identity ResourceMailbox -AddOrganizerToSubject $false -DeleteSubject $false


Install .NET Framework 3.5 on Windows Server 2012

If you try to install .NET Framework 3.5 on Windows Server 2012, using the Server Manager and accepting the defaults, you will get an error stating that the source files could not be found. During the installation process Windows Server 2012 does not copy the required files for installation of .NET Framework 3.5 as it did in Windows Server 2008 R2. On the confirmation screen after selecting the .NET Framework 3.5 Features, you’ll notice a yellow bar telling you that an alternate path to the data files needs to be specified. Near the bottom of the window is an option to Specify an Alternate Source Path. Click this and specify the following path, substituting X with your optical drive with the Windows Server 2012 media:

X:\Sources\SxS

Now the installation should complete without any issues.


Uninstall Apps from OS X

As nice as OS X is as an operating system, it is missing one important feature, an uninstaller for programs. Sure you can drag apps to the trash, but what about configuration files and other files left created by the app? The best program I’ve come across to uninstall apps is FreeMacSoft’s AppCleaner. Best of all, it’s free.


Exchange 2010 Move Requests With BadItemLimit Larger Than 49

If you’re performing a local move request in Exchange 2010 using the Exchange Console, it will only allow you to set a BadItemLimit up to 49 items. To allow a higher amount you need to do use the Exchange Shell. Use the following syntax, replacing SomeUser, ExchDB, and 75 with the appropriate values:

New-MoveRequest -Identity ‘SomeUser’ -TargetDatabase ExchDB -BadItemLimit 75 -AcceptLargeDataLoss


Completing a Failed Exchange 2010 Install on SBS 2011

If you’ve attempted an install and migration to Small Business Server 2011 only to receive the dreaded yellow exclamation point, indicating something happened during the process, you’re probably thinking that you’re going to have to go back and do the process over again. The good news here is you may not have to. If you take a look at the migration issues and it indicates that Microsoft Exchange 2010 didn’t install, then you can probably still salvage the situation. You’ll want to go ahead and generate the SBS Logs for the install process and scour through the Exchange install log looking for the reason it failed. Once you find the reason for the failure, you’ll need to find a fix for the problem.

If for example you find out that the install of Exchange 2010 failed because the Discovery Mailbox already exists, then all you need to do is delete the user from Active Directory Users and Computers, then you can proceed.

Once you’ve fixed the reason Exchange couldn’t install completely, you’ll need to manually kick off the install process. The installer for Exchange 2010 is located on the SBS 2011 Repair DVD, under the CMPNENTS\EXCHANGE14_SP1 folder. If the problem is fixed, then the setup should finish installing the missing Exchange roles.

Now there’s a few more steps that must be completed to finish the SBS 2011 install process and activate Exchange. The steps are outlined in this Microsoft KB: http://support.microsoft.com/kb/2527626

After you’ve ran the shell script to finish the SBS setup process and the hotfix to activate Exchange, you can reboot. If all has gone well you should be greeted with the expected green checkmark of success. At this point you can continue your migration process.


Importing PST’s into Exchange 2010

A fairly straight forward way has been introduced in Exchange 2010 to import PST’s into mailboxes from the Exchange Shell. Mailbox import requests were added into Exchange 2010 in SP2.

Give yourself permission to use Mailbox Import Requests:

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User Administrator

Import PST (Allowing 49 bad items before the transfer fails):

New-MailboxImportRequest -Mailbox Usermailbox -BadItemLimit 49 -FilePath\\SERVER\SHARE\SOMEPST.PST

Import PST into an Online Archive:

New-MailboxImportRequest -Mailbox Usermailbox -BadItemLimit 49 -IsArchive -FilePath\\SERVER\SHARE\SOMEPST.PST

More Info:

New-MailboxImportRequest
Get-MailboxImportRequestStatistics
Get-MailboxImportRequest


Speeding Up Exchange 2010 Mailbox Moves

Performing Mailbox moves in Exchange 2010 can be a rather slow process, moving at 3-4GB an hour. If you’re migrating a large store this is a long period of time to wait. Here’s how you can speed up the process significantly. I’ve used these settings on several SBS 2003 to 2011 swing migrations including from a 2003 swing server running in Hyper-V on a SATA drive. If you’re moving from something beefier than that I would suggest bumping up the MaxActiveMoves settings accordingly.

On the server you’re migrating to edit MSExchangeMailboxReplication.exe.config located in your Exchange bin folder (by default: c:\Program Files\Microsoft\Exchange Server\V14\Bin)

Find the following default values:

MaxActiveMovesPerSourceMDB = “5″   
MaxActiveMovesPerTargetMDB = “2″   
MaxActiveMovesPerSourceServer = “50″   
MaxActiveMovesPerTargetServer = “5″   
MaxTotalMovesPerMRS = “100″

Change them to:

MaxActiveMovesPerSourceMDB = “7″   
MaxActiveMovesPerTargetMDB = “7″   
MaxActiveMovesPerSourceServer = “50″   
MaxActiveMovesPerTargetServer = “40″   
MaxTotalMovesPerMRS = “250″

Restart Microsoft Exchange Replication Service


Importing a DVD ISO into iMovie ’09

Two simple steps are involved in importing a DVD ISO into iMovie ’09:

1. Mount the ISO

2. Inside of iMovie ’09 go to File, Import, Camera Archive, then browse to the ISO.


Binding Multiple SSL Sites to Same Port in IIS6

If you attempt to create multiple sites in IIS6 that use the same SSL port (by default 443), then you will get an error message when you try to start the second one stating “IIS was unable to start the site. Another site may already be using the port you configured for this site. Please select a unused port for this site.” To setup SSL on the second site you need to either use a different port or edit the metabase directly. II6 comes with a script that will allow you to edit the metabase and add the binding for the second SSL site

The script is located in the Inetpub/AdminScripts directory and will need to be run from there in the command prompt. You will need to know the site identifier for the site you want to add the binding to. You can find this in the IIS Manager, drilling down to Web Sites, it will be in one of the columns in the right pane.

Syntax:
cscript.exe adsutil.vbs set /w3svc/<Site Identifier>/SecureBindings “:<Port>:<Host Header>”

Example:
cscript.exe adsutil.vbs set /w3svc/1/SecureBindings “:443:server.example.com”

Once you complete this you should be able to start the site in the IIS Manager.