Bohack

When upgrade from Exchange 2000 or 2003 to Exchange 2007 you must perform a transition. Mainly because you can not upgrade the binaries on the Exchange 2003 box to 2007, 2003 is 32 bit and 2007 is 64 bit. During the transition you will need to have the 2003 Exchange Routing Group connected to the 2007 Exchange Routing Group. This will allow you to delever mail to recipients on both platforms and keep business continuity. You connect the two with a Routing Group Connector and I advise you use the Exchange Manager Console to manage them.

(more…)

I am starting to warm up to Exchange 2007 and found that anything and everything can be fixed through the Exchange Management Shell. Recently I transitioned an Exchange 2003 administrative group to Exchange 2007. After migrating the users from the Exchange 2003 to Exchange 2007, I decided to check to see if creating a mailbox is the same. So I opened the (ADUC) Active Directory Users and Computers MMC and ran through the creation of a new user and mailbox. When I went back to the Exchange Management Console the “Recipient Type Details” showed as “Legacy Mailbox”.

(more…)

Any day you can walk up to my workstation at work and find a command prompt open. Whether it is a Windows CMD prompt or a Linux Shell; I actually prefer it over the Windows GUI and over a KDE or Gnome on Linux. I can generally get more done in a few keystrokes then mouse clicks, especially when you need to start a task and have a log of the outcome.

(more…)

It has become culture to prepend the http:// prefix in front of a URL. In fact if you type the URL in most web browsers and hit ctrl-enter, the browser will prepend the http:// in front of the URL. The HTTP (Hypertext Transfer Protocol) works on port 80 TCP and is defined in RFC 2616. Since HTTP language is clear text over port 80 TCP that means that forms authentication will travel over clear text and can be intercepted. So it is recommended that HTTPS (Hypertext Transfer Protocol over Secure Socket Layer) be used to encrypt the session with SSL. HTTPS or SSL works over port 443 TCP and requires a private certificate be installed from a browser trusted Certificate Authority (out of the scope of this article).

(more…)

During the day I always have a command window open on my desktop. It helps get simple tasks done; like reseting a password for a user or opening an ssh session with a remote box. I have a multitude of Windows command or cmd scripts that help me through out the day. Often I may want to change or tweak a script and then the hunt is on… Which directory was it created in? I know that it is in the path; because I can just execute it without typing it’s full path, but where is it?

(more…)

I think we have all rebooted a server and then asked ourselves “Did it actually reboot?”. So we hunt through the logs for the event and then move on or reboot it again. During patch day for the servers this can be a real nag, knowing when something is back online so you can finish patching it; is key to getting the job done. So I wrote this little batch script a while ago to help keep track.

(more…)

Mass software installation is generally done with imaging of machines. The process is simple: a reference image is created and then software is installed onto it. Along the way we test the software, QC check the software installation against our environment, then regression test the software against accounts that will be used by our users. Finally ‘sysprep the image’ and then push out a gigantic image to the all the PC’s in the field and cross our fingers.

Some software just does not want to be imaged, so we find ourselves reverse engineering the software to make it work; licensing is usually to blame. This can sometime take weeks because it breaks other functionality. Many times we simply don’t have the time to image a PC and go through the entire process or it may be something that’s just not worth the time. Bohack’s rule of thumb is: less than 40 PC’s in the same location just sit down and manually install!

However that doesn’t mean we need to give up on automation. So I wrote what I call the ‘Automated Installation Framework’. It’s a simple VBScript with common subroutines and often just saves time behind the keyboard. It uses a VB command called sendkeys and saves us from clicking next, next, next…

To use it I recommend using a ‘Vanilla’ install of your current environment; so use the image in place you will be installing to. Virtualization undo disks help speed this process up, because you will find that you will be installing over and over again for the perfect rollout. Next start practice installing the program, as you write the keystrokes down required moving the install through its steps. Keep track of the time it takes and estimate the time for the slowest computer you have. Next create a domain account that is a local administrator or domain admin for the machines you need to install to. Create a simple profile for the user and drop the finished VBScript into the profile’s startup section (base of the profile\Start Menu\Programs\Startup). Now all you need to do is login as that user and as the profile loads and the startup section runs, your install will begin. Cross your fingers and watch the install!

(more…)