Austin Maliszewski's Blog

At Payton, we use Ghost to help us administer all the client PCs in the building. Each family of PCs gets its own image (with some minor variations since certain departments require specialized software that can’t be easily managed using GPOs) which is deployed every few months from a central server with multicast.

In the past, we’ve always booted the PCs with Ghost Boot CDs which allowed them to connect to the GhostCast Session. We didn’t have good luck with Ghost Console working properly, so we always did it this way. (Though I really want to start using WDS). However, recently, we acquired 100 notebook PCs that don’t have optical drives. Obviously, this was a problem. We were either going to have to use a USB CD drive or a USB floppy and neither would have been pretty for imaging 100 PCs.

There are several ways of network booting for Ghost. I’m going to go over two ways. One is with all free or shareware software and the other, is the way we ended up doing it and that’s with 3Com Boot Services since Symantec Ghost 8 Corporate includes it. Let me say that that software is a piece of work. It has a UI dating from the Windows 3.11 days. However, it actually works, when you get around its quirkiness. (I picked the 3Com route because you can configure the PXE server to run in DHCP Proxy mode which was critical since we don’t have any control over the DHCP server.)

Instead of me going over everything with the free/shareware software way, let me just provide a link. His instructions are great and got me a working setup. (Just don’t use any of the included software, it’s a few years out of date). Link from Damian Jackson at Lilydale Heights College. Point of Interest: The only drive letter that the Ghost Boot Wizard is willing to work with for creating the floppy image is A:/. You might need to disable your system’s actual floppy drive if you’re not using real disks (or don’t have physical access to the server). That took me hours to figure out.

It’s also probably not worth me going over the 3Com Boot Services way since it comes with a perfectly good manual on the CD. However, there are a few things which are covered in the manual, but not inherently obvious if you don’t read the manual. The rest is straight forward and you probably won’t have to read the manual. This is the brief version of everything.

First off, you need to create a Network Boot Image using the Ghost Boot Wizard. You can probably figure this out. Make sure to use the PXE Network Driver. I made two images. One has no command line parameters (which I called Ghost Manual) and the other has the parameters “-ja=[sessionname] -sure” where [sessionname] is equal to the name we use for our GhostCasting sessions. This I called Ghost Automatic since it automatically connects to the session.

Now you need to prep 3Com Boot Services. On your Start Menu under 3Com Boot Services is the 3Com Boot Image Editor. Open that up and select “Create a PXE menu boot file”. Create your menu file. Here’s what mine looks like.

PXE Boot Menu in 3Com Boot Image Editor

When you’re done go ahead and save it. You can name it if you like or just leave it as “mba.pxe”. The next step is to edit the BOOTPTAB file. Which you can do by opening the appropriately named BOOTPTAB Editor. This whole BOOTPTAB thing is a little clunky. The default BOOTPTAB file has a couple of entries. Go ahead and nuke those. Now, go to Edit and Add Host. This is where it gets a little weird. This is how you fill it out:

Adding a new host into BOOTPTAB

Yes, those are really question marks. You can also specify a MAC address, but putting in all question marks serves as a wildcard to allow all clients. Hit “Ok.” Now your BOOTPTAB file should look like this:

Sample Configuration

Go ahead and save that. Now, you can launch the PXE Server and the TFTP Server. (Both must be running. You can make them services if you’d like.) When you first launch the PXE Server it will check to see if the PC you’re running it on is a DHCP server. If it’s not, it will ask you if you’d like it to be a DHCP Proxy. Tell it that you would. You’re all done on the server side.

Now, go to one of your client PCs and tell it to boot from LAN. If you did everything correctly, you’ll get a menu that looks something like this (depending on your configuration).

PXE Boot Menu

Happy Ghosting!

So, it’s summer, and in theory, since school’s out, I’m supposed to have more time. Actually, I seem to have less. I’ve been so busy lately (with some really neat things and some boring things) that I haven’t had time to blog about them.

So, in the next few days, I’m going to force myself to blog about a couple of things.

1. Terminal Services: Yes, I will actually post that guide to setting up TS and making it work.
2. Network Booting Ghost
3. Doing a network boot when you don’t control the DHCP server.
3. SSL Certs are a PITA and kind of stupid
4. Windows 7 and 2008R2
5. Books
6. TI Nspire CAS stuff

I’ve been using the Windows 7 RC the past few days and I’m generally impressed with how well it runs. For one thing, it runs quite comfortably on only 512MB of RAM. It even runs nicely in a VM, with no real performance issues. It’s highly usable, even when virtualized, which is more than Vista can say. It’s also really pretty. The UI is really nice, in a way, it’s much more like OS X. The taskbar has been totally redesigned, it’s now like the dock in OS X.

Within the next week or so, I’m going to switch my primary PC to Windows 7 and we’ll see how it goes. I’ll write more later.

For the past few days, I’ve been fighting trying to rearrange the order of RemoteApp programs in Web Access. I figured out that it was sorting based on the name of the RemoteApp’s RDP file. I just couldn’t figure out how to change the name of an App’s RDP file without breaking everything. Tonight, I was installing a new app onto one of my TS machines and I happened to notice that when you right click on an App in RemoteApp manager and select properties there is a field called alias. This alias field corresponds to the name of the RDP file. When you change the name here, it will rename the file and update Web Access. By changing the names here (and knowing that Web Access goes in alphabetical order of these aliases) you can rearrange the order of RemoteApps in Web Access.