Posts Tagged ‘macosx’

Imaging a Lab with DeployStudio

September 2nd, 2011

Imaging is a great thing..it really is. When you have more than 2 computers, imaging becomes your best friend…and if you buy new machines or one of your older machines dies or gets messed up, it saves so much time. I have a complete backup ready to deploy at all times for both Mac and Windows.

I image my lab once a year. This ensures that I have the latest updates for every machine for all programs, but it also cleans out the old stuff from the previous year that builds up over time. Apple makes imaging very simple by installing a NetBoot feature on all of their machines and including a NetBoot server installed with MacOS X Server. In the past I used Bombich NetRestore, a free AppleScript based program that helped make NetBoot image sets and helped with deploying them. Mike Bombich stopped making NetRestore and suggested everyone to try DeployStudio for imaging..so I did. I must say that DeployStudio is an amazing program especially for a free program. It’s also very simple to get running and fairly robust. In this post I’m going to go over image creation, setup, and deployment with DeployStudio (DS) and also go over some issues I encountered and how I fixed them.

Creating the NetBoot Set

The first step to any Mac NetBoot is the NetBoot set. What the set is is a basic image file that includes all the tools your computer will need to read the image, copy the image, and even run checks on your computer even if you’re not imaging. It’s a very basic MacOS install that resides on the server. DS creates these images for both PPC and Intel machines in the same set, so any Mac can boot from the same set. After installing DS on your server you can open the DS control panel and begin setting up your system AND create your NetBoot set. I will not be going over server setup in this post, I may save that for a later time.

The DeployStudio Control Panel

When you open the control panel you should launch the assistant (you can also find it in /Applications/Utilities). When the assistant opens you select “Create a DeployStudio NetBoot set and continue. If you’re running the assistant on a computer other than a server you will see this:

DeployStudio DHCP Setup

If you plan on using a server to do the deploying, you can skip this, if not, you’ll have to setup a DHCP server. This depends on your setup, for my case I can skip this. The next step allows you to name your set; set the name and unique identifier to whatever you wish, (unless you have multiple NetBoot sets). When you click continue you will tell the set where the computer should log in and look for the images and workflows.

My settings...

more settings...

The settings above are MY settings, yours will be different. The login and password for mine are supplied by the LDAP server. The final step is the actual save location and creation of the image. Pretty self explanatory. It takes about 5-10 minutes.

Completed NetBoot .nbi file

After image creating is successful you’ll have a nice .nbi file in your save location. This file is basically an image file that contains the bootable images for PPC and Intel as well as the basic MacOS system with some basic utilities like Disk Utility, Terminal and Startup Disk. It’s roughly 2.5 GB and it should be placed on your server in the NetBootSP0 folder (It’s located in [Volume]/Library/NetBoot/). Inside the NetBootSP0 folder will be other folders which DS created during install, these contain various other things for DS and also house your images. I will go over image creation next. This is where we will be able to test to see if your NetBoot Server and set are both working.

Creating Images with DeployStudio

Creating the images is an extremely simple task once you know what settings you need. I will explain the setup with my current settings but attempt to go over most of the other ones.

To start the process, boot your mac and hold the ‘N’ key down during power on, this will perform a network boot (REMEMBER: Your computers must all be on the same subnet, this is the only way to do this without messing with a lot of things!) If your computer boots to the DS screen you will see the DS Runtime Window.

This window shows all of your available jobs in DS. There are a few default jobs that come with DS, we’ll make our own later for deploying. For now we’re gong to select “Create a master from a volume.” Click the Play button at the top and you will come to the heart of the Image creation.

My Image Settings from a PowerPC computer

This window is probably the hardest window we’ve seen so far. First thing is to choose which drive you will make an image of from the dropdown menu. I’ll start with my MacOS partition. After selecting the correct partition I name the image something like 2011_09_02_Intel_lab and leave other settings alone. The keywords are not very important unless you have a lot of images. I usually select Compressed for the type because it saves space and it gives a much faster restoration. Access group is what you would have set in your initial DS setup that I did not cover.

Format is what kind of image you are making. Since I’m doing a MacOS install the Format will be HFS+. I normally select “Auto Detect” but if you want to have HFS+ Journaled, Case-sensitive or both you may want to change it because it will always auto-detect HFS+ without journalising.

Once my settings are correct I click the Play button at the top and the image making process begins. This will take a lot of time depending on the size of the image being created, a 100+GB image will take roughly 2 hours (sometimes more, sometimes less, depends on the machine and network) and it will then compress the image (my images get compressed to about 75GB from 128GB…compression rocks!).

Masters in the NetBootSP0 Folder

After image creation you will see the .dmg file in your NetBootSP0/Masters/HFS folder. (Note: I just found out that new versions of DeployStudio won’t show your images in DS Admin unless you have .hfs in filename before the .dmg, it will automatically add them during image creation, but if you have old images, just add the .hfs right before the .dmg extension).

You can use this same process to create NTFS, FAT, and EXT4 images. Follow the same steps but make sure you leave the Format as “Auto-Detect.” After creating a NTFS image it might take some time to show up in DS admin, this is because some server-side tasks may need to be done, it will show up when that is complete. NTFS imaging requires a little more setup in DS admin beforehand…again, I will not be covering that in this post.

Making Workflows to Deploy Images

DeployStudio comes with an administration program where you can manage images, workflows, packages, scripts, and see progress of NetBooted computers. You can also set up all of your computers in it before hand (names, network settings, licenses, etc) and set up automation for all of your systems so if you want a computer to automatically format and re-image when you NetBoot it, you can do that (please don’t think that’s a great idea…just saying). To start setting up workflows you’ll need to open DS Admin, it’s located in /Applications/Utilities. Enter your server credentials and you’re presented with the DS server information.

The window that opens first is the current (or previous) activities. In this window you can watch and control the computers that are currently working in DS. ou can also see what jobs they were doing, and how far along they are. This screen is very helpful when you have DS running on many machines.

I am going to explain how to setup a dual-boot Mac workflow. The default jobs are very helpful at getting you started, I’m going to start from scratch. To create and edit workflows we’re going to select “Workflows” from the left sidebar and begin setting up our job. Click the “+” button at the bottom and you will be presented with a new blank job. Then click on the little “+” button next to “Drop tasks here.”

Creating a new workflow

The first thing to do is to drop the “Partition a disk” task from the left side to the drop space. Then you should select “Mac OS X + Windows” from the Apply layout template dropdown menu. Resize the partitions to suit your needs, make sure your images will be able to fit on the partitions you make for your drive. I normally do 75% Mac OS/25% Windows, I also normally Automate this process, your mileage my vary.

The next step is to drag the “Restore a disk image” job from the left and drop it after the partitioning job. Your MacOS image should ALWAYS be first of else it will not work. Select “Enter value…” from the Target volume section, then select the “MacOSX” option from the menu. Set your Image to HFS and select the appropriate image from the menu (the one you created earlier). Now, for the options you can read from the image below how to set those. If you’re imaging Mac OS 10.7 Lion you should check “Restore system recovery partitions” but I don’t need this.

My HFS Settings

You may also notice Multicast settings, you can set this up if you’re brave, I don’t need it so it’s ignored. Your HFS partition is complete, now on to Windows.

Drag the “Restore a disk image” job from the left and drop it after the first restoring task. Select “Enter value…” from the Target volume section, then select the “WINDOWS” option from the menu. Set your Image to NTFS and select an appropriate image from the menu again. Settings for Windows is relatively the same as HFS with some exceptions; you should check “Expand restored NTFS partition” and uncheck “Set as default startup volume” unless you want to have Windows as your default. You’ll also notice that all of these tasks are automated, this is so you can boot the computer, select the job, and walk away without intervention.

DS NTFS Settings

Now, you can add more jobs to the workflow such as AD binding, or software updates, but this setup is the basic setup for a dual-boot deploy. Now just rename the job by clicking the name in the top with the other jobs and rename it, you can also add a short description of the job. Your workflow is now complete! Now it’s on to the easiest task…deployment!

Deployment

I say this is the easiest part because it really is. If you have everything set up properly, you should have no issues.

To deploy the image to the computers, boot the machines again pressing the ‘N’ key, when the machine boots to DS you can select the newly created Workflow and press the play button. If you automated everything, that’s it..it will partition your drive and load the images to those partitions. After the job is complete your computers will either tell you it was successful (or failed…more on that below) or they will reboot. If the task was successful, GREAT! Reboot the machines, they will run the final scripts in MacOS then reboot again…MacOS is done. You only have one more thing to do and that’s configure Windows. I won’t go into this because it’s going to be different for everyone, but you will have to activate windows and any other programs that require it because Windows will not keep the activation after imaging.

Issues?

Now, not everyone will be so luck to have a successful run…if you run into any issues visit the DS forums, they are very helpful and pretty speedy. I had one issue that just drove me nuts. When I ran my deployment script the MacOS partition would go fine but once Windows hit it would fail…everytime. DeployStudio keeps logs for every computer on the server, so I took a look and noticed the following errors:

[Thu Sep 1 14:41:15] dyld: unknown required load command 0×80000022
[Thu Sep 1 14:41:16] -> invalid starting block value () defined in MBR for partition /dev/disk0s3.
[Thu Sep 1 14:41:16] Check your partition map. You need to define at least one DOS/FAT partition in order to get the MBR automatically in sync with GPT.
[Thu Sep 1 14:41:20] -> Restore action completed.
[Thu Sep 1 14:41:20] Restoration failure (elapsed time: 0.24 minutes)

I posted in the DS forums (topic link) and in a matter of hours the admin of the forums posted a solution:

Sounds like the custom fdisk command fails on 10.7 DSS netboot sets. You may try to remove the one located in your netboot folder at /Applications/Utilities/DeployStudio\ Admin.app/Contents/Frameworks/DSCore.framework/Resources/Tools/fdisk.

So I tried this and BOOM, successful. It’s great when a developer helps with products so quickly…and I’ve only usually seen this with free or open source projects. So if you’re having issues, the forums are key.

I hope this post helps people out with Mac imaging and deployment. If you have any other questions or issues feel free to ask in the comments. If this post helped you or think it will help others please feel free to repost and share away!

2 comments »

Posted in Guides, Software

Tags: deploystudio free macosx servers software windows xserve

More TUAW Stupid & Mac vs Win..again

May 27th, 2010

I read a few tech blogs on a daily basis; Engadget, Bynkii, and of course, TUAW (The Unofficial Apple Blog). I like reading about new technology, and I like reading about people using both new and old technology as well. I come across a lot of good blog entries on these sites… and then I come across something like this post.

TUAW blogger, Steven Sande, recently wrote an entry entitled: “My weekend Windows experience, or why I love Apple so much”. This is just a long title for some Mac fanboy bashing Windows like it’s 1998 again. Posts like this are a dime a dozen, and some of them have valid points, but this one just really got me annoyed for many reasons.

Now, if you read the article you’ll know that this guy just bought a “rather inexpensive Chinese-made” Wifi webcam from Amazon that claimed it was compatible with “Apple Mac and Windows”. After he gets the product he finds that it first needs to be set up in Windows before it can be used on Mac, therefore the company lied which means that a) the camera you bought is made by a shitty company in China, b) you should just send it back and get a real camera, and c) anything you do after this point is your own fault, right? Not to this guy, he decided to set it up in Windows Vista, excuse me, a Windows Vista VM on his Mac. This is all fine and dandy, but so far nothing is here about why he enjoys Mac over Windows. Now, his “process”:

3) Fire up Windows, then realize that I can’t use the camera software install CD since it’s one of those mini ones that were so popular in 1998. They don’t work in slot-type SuperDrives. Need to download the software from vendor’s website.
4) Start up IE7 in Windows.
5) Can’t get to downloads page from IE7 so download and install Firefox.
6) Go to vendor site, get to the downloads page. Can’t download the software until I download and install the Flash plug-in.
7) Install Flash Player.
8 ) Download the software, finally. It’s an .rar archive.

Now, all of these steps are pointless. The first thing I notice is that he’s in Windows, which is installed on his computer, and he is using IE7 and doesn’t have Firefox installed already, why he didn’t have it installed is a mystery to me, but it begs the question why couldn’t IE7 download it? This is another problem with the camera’s manufacturer, not Windows. Same with the next step, installing Flash; why is Flash needed by this vendor to download a file, and why the hell wasn’t it installed already anyway? I suppose you don’t want to install all of this extras stuff on your Windows VM because you want to save space for your Mac, but these are essential things for any Windows install, so that’s your fault, not Windows.

9) Windows has no idea what an rar file is. I have it “use the Web service to find the correct program.” I find out that WinZip or StuffIt Expander will work.
10) Realize that WinZip is a program that, with all the add-INS, will cost me almost US$37. Didn’t it used to be free?
11) Go to StuffIt site and download free StuffIt Expander. Wait while McAfee scans for viruses.

These steps here made me want to smack this guy through the machine. First, if you claim to have years of experience working on windows machines (In the article: “I am familiar with Windows. Way too familiar, as at one point in my career I was a project manager on a 12,000-seat Windows deployment for a large enterprise.”) you would know to just get WinRAR or 7Zip and you’d be done with this stupid mess, but no, you use the “find correct program online” option like a moron and decide to download StuffIt (a pain in the ass in it’s own) instead of WinZip (which you can use free forever). And that last line about McAfee just makes it even worse. You were the “project manager” of a large enterprise deployment and you’re using McAfee?

12) Install StuffIt Expander. “This may take several minutes” it says.
13) Installation continues for an incredibly long time, most of which is marked by a status message that doesn’t change. Considering taking up smoking. Read War and Peace cover to cover while waiting for installation to complete, then build a 1:1 scale model of La Sagreda Familia out of toothpicks. About to perform a self-appendectomy when the installation finally finishes. Put away the X-acto knife and vodka.
14) Trying to reinstall StuffIt when Windows tells me in needs to activate. That’s perplexing since I installed and activated this legal copy of Windows Vista Ultimate weeks ago. Decide to at least try reinstalling StuffIt before going through activation again.
15) StuffIt Expander installer won’t run since it says that there’s already another installation in progress. System monitor shows no other application is running.
16) Restart Windows. Or at least try to. It takes forever to shut down. Finally Force Quit VMWare and hope for the best.
17) Re-launch VMWare, which unfortunately comes up in Windows shutdown mode. Finally find the Shut Down command in VMWare, then restart Windows Vista. It’s now 7:55 PM. Windows Vista plays its 4-tone startup tune, which I salute with two raised middle fingers.
18) Start up the StuffIt Expander installer again. Get an error message. Re-download the installer and try again, this time sacrificing a chicken while starting the installer. The installer takes its good time, but finally shows a completed installation. I feel sorry for the chicken, but happy that StuffIt Expander is installed.

Okay, you’re installing StuffIt inside of a Windows Vista VM and it’s taking forever and you’re surprised? You’re also surprised that it takes forever to shutdown, and restart in a VM? Okay, you’re blaming Windows for running slow in a VIRTUAL ENVIRONMENT when it’s not really designed to be run in one. Ever think to blame VMWare for this? Or StuffIt for making a bad installer? Oh right, you’re a fanboy.

Windows asking for activation means one simple thing, you didn’t activate. I know it says you did, but you didn’t. That is your fault. Sure, it’s a very annoying occurrence to have to activate Windows, we all hate it, but it’s your own dumb-ass fault.

19) What was I doing before all of this? Oh, yeah – I was trying to unzip the webcam installer. This goes well until the unzip crashes. I see the installer on my desktop, so I double-click to install. This installer runs quickly, but I need to reboot the Windows virtual machine.
20) Weeping uncontrollably, I wait as the virtual machine lies to me about shutting down. It’s now 8:09 PM. I wait, and wait. Did I mention the waiting?
21) I’m so bloody tired of waiting for the shutdown that I invoke the Shutdown menu item again. Windows reboots again.
22) Double-click the webcam software. After I nearly have a heart attack when it temporarily can’t find the .exe file, it launches. This program is supposed to find a camera on the network and allow me to change settings. It’s doing nothing, so I decide to start pinging addresses on my network from Safari. I find my printer’s built-in web server, but not the webcam.
23) While I’m playing on the Mac, Windows mysteriously reboots itself. WTF?
24) I figure out that Windows thinks it is on another subnet. I look at some of the glowing reviews on Amazon and see the key phrase “connect to the camera over Ethernet the first time.” Nice of the vendor to put that in the docs. I’m tired. It’s now 8:58 PM. I decide to try this tomorrow on my old iMac since I have work to do. I’ll set up a small Ethernet network using a router I have, and hope that I can get this to work.

Again, most of this is the camera vendors fault and the fact that you’re running a VM.

Number 24 wouldn’t come naturally to someone who isn’t a tech person, but since this guy claims he is one, he should already know that when running in a VM you’re on a fake subnet created by the host to allow you to share the network connection. And the fact that you didn’t setup the camera over Ethernet FIRST is beyond me. For someone who knows technology this is pretty fucking stupid. Also, what kind of tech person doesn’t have a fucking network setup in their house? How do you not have an extra Ethernet port somewhere, ANYWHERE in your house? What the hell?

25) It’s now the next afternoon. I set up the old Linksys router, grab a few Ethernet cables, and fire up the camera app on the old iMac under VMWare and Win XP. Not surprisingly, Win XP works much better than Vista and within about 5 minutes I’m seeing the camera “anonymous” in the camera app.
27) Reading the tiny print in the poorly-translated user manual for the webcam, I see that the vendor recommends using IE to bring up the built-in administrative web page and set up Wi-Fi. I double-click the name of the camera, and I’m immediately rewarded with a login screen for the admin web page. I log in using the default user ID and password, and then watch as IE7 proceeds to block the various controls that are trying to load.
28) At this point I’m discouraged and shouting four and more-letter expletives at IE7. I decide that it’s time to grab my spouse and go out to eat (and drink) away my frustration. A few beers later we’re back home and I download Firefox onto the virtual Win machine.
29) I launch Firefox, go to the IP address of the camera, and become very happy when the camera controller loads properly and responds to my commands.
30) With the webcam finally up and running, I tell Windows XP to quit. Soon I’m greeted with a happy message that says something like “Windows is installing update 1 of 37. Do not shut down this machine.” I wander off.
31) Two hours later, the message says “Windows is installing update 31 of 37.” I may never get to shut down Windows.
32) Another hour passes. The message hasn’t changed. I decide that Windows XP has locked up, and I invoke the magic VMWare virtual power switch. Who knows if the flippin’ thing was updated or not?

Alright, you decided to ditch the Vista VM and go for a XP VM, good job, it only took you a day to figure that out. Now you’re going to try IE7 again and you say it’s “block[ing] the various controls that are trying to load” and you’re now discouraged to use IE7? Guess what, that means the camera vendor fucked up again, not Windows. Windows is in fact probably doing you a nice favor by blocking this vendors’ shitty software. Not to mention, you can tell IE7 to load those controls fairly easily. Also, if you’re using a web browser to set this up now…why not just use Mac OS? As a matter of fact, why didn’t you do steps 1-20 in Mac OS? All you had to do was fire up Safari and download the RAR file and open it with your StuffIt expander in Mac OS and guess what, you’d have taken like 4 hours out of this entire cluster-fuck process you went through. Again, if you’re a tech guy you should know this shit.

The last few things are just asinine. You’re blaming windows for taking forever to shutdown again (IN A VM!) because it needs to install updates. Well, correct me if I’m wrong, but you are supposed to install updates. If you’d boot into your VM more often to secure it with updates you wouldn’t have to wait an hour to install 37 fucking updates.

Then this ass-hat goes on to put this in:

But the point of this entire exercise was that if Apple had ever stooped to selling Wi-Fi webcams, the installation process would probably be like this:

1) Plug your Apple iCam into a wall socket.
2) Launch the iCam utility software on your Mac or Windows PC. It’s included on the CD that came with your device.
3) Your iCam appears in the “cameras on this network” list. Highlight the camera you wish to update.
4) Give the camera a name, and click save. Note the web address that is now listed on the page — this address is where you can point any web browser in the world to view your camera and listen to what’s going on in streaming stereo audio.

Guess what, if you bought a better camera instead of your cheap Chinese piece of shit (your own words only shortened) you could have done this. Just because it’s not Apple doesn’t mean it wouldn’t be simple. He also goes to bring up the virtual machine issue:

And I’m certain that someone will say “A real PC wouldn’t have done that; you’re running a virtual machine on a slow Mac.” Wrong, this type of thing has happened to me many times on real PCs as well. This isn’t a slow Mac; it’s a quad-core i7 iMac running 64-bit Windows Vista Ultimate.

Guess what? They’re right. You wouldn’t have had half of these issues. I don’t care what kind of processor you have, running in a virtual environment is never the same speed or experience.

So this bothers me for a few reasons as I stated above; first it just shows how stupid people like to blame their fuck-ups on technology that they obviously don’t know. Whether it’s some moron complaining about installing updates in Windows when they haven’t updated their computer in a decade, or it’s some guy saying “Macs are dum cuz they don’t have 2 mouse buttins” it’s all the same idea. You bash the OS you don’t like with stupid shit like this.

This also upsets me as a Mac user in general. According to Steve Sande’s bio on TUAW:

“[Steve is] A 52 year-old Apple geek, Steve has been writing online since 1986, when he started up a Mac Bulletin Board System (BBS). He’s been a Mac user since ’84, was a Newton Developer, and has been involved in the mobile computing space since 1993.Steve lives in Colorado with his rocket-scientist wife of 30 years, a cat, and many Apple products.”

This guy has been working on computers since before I was born, and I guarantee that this guy has been using ONLY Macs since then. So he’s not a Windows person: he is an Apple user. He knows what Apple people deal with from people when it comes to tech support for products, and what people think of Apple users (hippies who don’t know how to use a computer…blah..blah) and guess what; it’s because of guys like Steve Sande that people think this. You bitch and moan about Windows problems and then go to say “Well if this was Apple it’ll be like this and so much better.” Yes, Apple makes it super fucking easy to setup things with them, but if you notice one simple thing you’ll realize how they can do this: They are all made by the same company. Surprise! Apple products work very well with other products made by Apple, they’re designed for each other! Do you know how easy it is for me to set up my HP 1020 Laserjet in Windows over network? It’s so easy that I probably don’t need to explain it (plug in, turn on, find on network, done). It was a nightmare in Mac OS. I have to download third-party drivers and then an extra program just so it can find the printer, then I have to change some folders around until it works properly. So am I going to bash Mac OS because they made it so hard for me to get my printer working? Fuck no. I’m blaming HP because they decided to stop support for Mac OS 10.5.

I see things like this everyday online, in both directions. Go on an Apple-based blog and it’s WINDOWS SUX! Any gaming site and it’s GET A REAL COMPUTER! MACS SUX! Turns out, the users suck, not the machines. If you’re not smart enough to do something or to realize that something you have just won’t work with your system the don’t blame Windows or Mac OS, blame yourself.

No comments »

Posted in Rant

Tags: apple macosx stupid tuaw windows

Upgrading from 10.4 Server to 10.5 Server

June 1st, 2009

As I’ve mentioned before, I manage 2 Apple Xservers and a lab full of Macs. When classes ended for the summer I decided to upgrade our Tiger server to Leopard. This was a task that I knew was going to be a lot of work especially because I was consolidating our old Dell web/mail/DNS into the Leopard machine. These computers were set up well before I came into the picture, and I was still learning new things about them as time went on. For example: I didn’t know that the old system (Wanda) ran another DNS on top of the university DNS. Confusing.

So, I decided to do this some time ago when I realized that every time the server would restart passwords would be locked out. This was an issue with the Kerberos setup in Tiger which was half broken by the time I got here. Long story short, I wanted to start over, so I did.

Upgrading from one system to another on a server s never an easy task, and Leopard was definitely no exception at all. I’ve upgraded Linux systems much easier than this. I decided to make the image in the lab one of the PowerPC G5s we have (the server is a G5). Here’s a fairly quick rundown of how I got everything to run like I wanted to.

Install 10.5 Server fresh selecting “Advanced Setup” from the choices offered. We’re going to be hosting a ton of services on here and I want to be able to configure every single one of them myself.
Install ALL updates available BEFORE SETTING ANYTHING UP! This is something I always do. it’s so much easier to start setting up the server after it’s completely updated. I don’t want to set up then have something break because the new update fucked it up and believe me, it happens. During this time I also updated XCode to 3.1.x so I can build anything with MacPorts when needed.
Next I needed to re-install or re-compile PHP5 so I had GD and MCRYPT. Instead of recompiling it I decided to install the Entropy PHP build which comes with all that jazz installed plus a few more things. All I have to do is disable the apple libphp5 plugin that comes wth Apache2. Done.
Next I installed the Autodesk Maya FlexLM license server. This was a bit annoying since there technically is no Leopard build from Autodesk. I decided to download the License server from Autodesk and go into the installer package and snoop around a bit. I found a conf file that I could edit to allow it to avoid checking for 10.5. That allowed me to install part of it, but the license server wouldn’t go. I finally just went into the package and took the launch daemon out and the library and just copied the files to their respective places in the system. Rebooted and it worked fine.
I decided to setup phpmyadmin as well as Webmin for administration. Webmin is great, I’m very used to it and it’s very lightweight. Phpmyadmin is obvious. I copied the folders to /etc and redirected the links in Apache using server admin and ran the setup scripts. I also installed the OS X Web-based open directory password changer while I was at it. All worked fine.
Next I did an rsync from the old webserver for the website. Copied everything over, dumped and restored the MySQL databases and users and voila! Web is back.
I rsync’ed the Mailman mailing lists from the old server. This was another issue. The data, archive, and list confs were all compatible; however, the symlinks on the copied lists were not working because they were still pointing to the old server model. I couldn’t really change the links without mailman complaining so I did some workin around this. First, I copied the archives from the old server to the new, this worked fine. I then exported the lists using server admin export AFTER I copied the lists from the old server. This gave me all mailing lists but nothing else, which is what I needed. I removed all the old lists and confs from the system but left the archives in place. I re-imported the lists that I exported from server admin and BING! All mailing lists recreated the links and all lists were back to their working state. Archives came over, user lists came over, and no complaining mailman.
After that was set I copied all of the DNS settings from the old server and put them in the new DNS. I also gave an updated list to Poly’s IS and disabled the now deprecated IDMI nameserver. Everything was now BXMC. This was about the time that I finally turned off Wanda, the old webserver, for good. Wanda will be reconfigured for Hans.
I enabled everything after I turned off Wanda; DNS, Firewall, DHCP, Web, Mail, etc. DHCP and Firewall were imported over from the Tiger install, so that was nothing.
I attempted to restore the open directory database from the Tiger backup. It wasn’t working, at all. I was getting frustrated because now I was thinking I had to put every user in by hand. I finally figured out that I was attempting to restore the LDAP database using the new kerberos realm and new LDAP searchbase. This won’t work because the backup is using the old one, they just won’t talk. I tried to restore using our old searchbase and realm and it worked! I did attempt to change the realm and searchbase with no success, so for now I’m leaving it at IDMI. No one will see this except myself and the systems so I could not care.
With OD working again I tested all logging into the wiki, website, lab machines, afp, etc. All worked after a password update (which all users will need to do unfrotunately).
The final bit was to get the NetRestore working on the server. I wrote about using NetRestore by Mike Bombich here, and how it reached EOL. I stated that I would continue to use it until it stopped working….well, it stopped. I was sad to see this actually, but our mac’s wouldn’t boot from the system anymore. They all failed for some unexplained reason. I decided to give the one Mike Bombich recommended a shot, DeployStudio. Installing DS was easy, just a simple pkg file. Setup was even fairly easy. I ran the server setup on the server and that’s really it. I used carbon copy cloner on a labmac to create an image (even though DS allows you to create one in the NetBoot screen, it didn’t work) and the NetRestore was back working. I actually would like the wrote more about DS in the future. I am very surprised with how well it works and the features it has built in. But that’ll be another story.

So this entire process took me 4 fresh installs on a lab machine before I got the image the way I wanted it (about 4-5 days). It took 45 minutes to copy the image from the external hard drive to the server, and took about 3 days of tweaks to get everything running smoothly. The entire experience was pretty painless, but it kept me busy for the entire time. I will be re-imaging the secondary server again (it was upgraded to Leopard before the main server last summer) so that I will now have everything fresh and clean for the next semester. Here’s a nice shot of server admin with everything running nicely:-)

If anyone reads this and needs help with a server setup and/or upgrade from Tiger to Leopard please feel free to comment or ask me any questions about it because I’ve seen every issue now with the server and I now know how to get around a lot of things with it.