Mavericks Server Deploy Studio Multicasting tests

I read the wiki page on multicasting from the Deploy Studio wiki pages.

When I'm imaging one machine, I'm getting a download rate of 8.5MB/s, and a variable write rate, but it is a compressed image. When I put 5 machines on, I'm getting about 1MB/s download rate, which is too slow for my liking, especially with a 89GB Image file.

The server is a new (2014 - July) mac mini server, 8GB RAM, 2 x SSD 256GB, Mirror RAID. Deploy Studio 1.6.11

Repository is stored on another server, on a different subnet which might cause issues? Shared via CIFS.

The Server is on GigaBit LAN so I'm trying a 10MB/s stream rate to start with.

The computer suite I'm testing on are Mac Mini's from 2011, 4GB RAM, 500GB SATA HD's.

To get the Client Write Disk Speed I put in this command in the terminal:

sudo dd if=/dev/zero of=/tmp/test bs=1024 count=1048576
Password:
1048576+0 records in
1048576+0 records out
1073741824 bytes transferred in 18.062331 secs (59446470 bytes/sec)

This converts to 59MB/s

Test 1

clients: 5
Stream Data Rate: 10MBs
Client Disk Speed: 43MBs

Conclusion: Got about 20 fails on each computer before 2% of a 89GB compressed image.

Realised I didn't scan for restore. At this point I scanned the image for restore using Disk Utility on Server.

Test 2

clients: 2
Stream Data Rate 10MBs
Client Disk Speed: 42MBs

Conclusion: Got about 7 fails on both machines before 2%

Test 3

clients: 16
Stream Data Rate 6MBs
Client Disk Speed: 38MBs

Conclusion: Got 2 fails in the first 2%, but 7 more fails in the next 6%. Interestingly, 7 out of the 16 started doing the recovery partition first, and as it was so quick, got onto the main image after the rest were over 2%. This might explain the packet loss. Getting a consistent 13 fails per 8%. Not sure if this works out at less then 20% or more? Seems to have failed to reimage 3 out of 16, which is good.




For the next test I wanted to see if having the images on the server itself would speed things up. I setup the repository in NetBootSP0 in /Library/Netboot/NetBootSP0

Test 4

Clients: 4
Stream Data Rate 6MBs
Client Disk Speed: 38MBs

Conclusion: 1 machine out of 4 got 20 fails before 2%, but then only got 2 more for the whole restore. Must have been a network spike or something. The others report very little (smallest so far) fails! Yay. Think I'll try and speed it up for next test.

Re-imaging Windows 7 on Apple Macs

So, we are now trialing a newer system for deploying Windows 7 on to our Apple Macs. Previously we've used Deploystudio, but as our Apple Server is too old, it is no longer up to the task.

For the rest of the PC's we use the Microsoft Imaging technique (whatever this is), and we're trying it with our macs.

Here's a step by step of what to do with the installer disk:

1. insert disk
2. set the default boot disk to be Windows (assuming Windows was previously installed)
3. reboot and hold ALT
4. select the CD
5. Press ANY KEY
6. log in with own credentials
7. Select task sequence
1. to determine which volume to boot from you need to run DISKPART. Type:
1. SELECT DISK 0
2. LIST VOLUMES
3. SELECT VOLUME (type the volume number)
4. LIST PARTITIONS
8. Select to install BootCamp drivers
9. Put name, domain details in
10. Go!

Imaging Windows XP on a Mac - filling (expanding) the partition

So, came to a machine today which I'd just re-imaged with windows XP using DeployStudio. Windows thought the partition was only 30Gb's  but was actually 110GB's. I had seen this before but never written down how to fix it.

First thing I tried was the Disk Checking utility. This did not fix the problem.

After this I didn't know what to do. I turned to google and found this forum answer. Turns out when re-imaging there is an option to "Auto Expand" windows to fill the partition but sometimes does not work. To fix, use WinClone. Unfortunately the latest version of WinClone now costs $19.99, but the older V2.2 was free. I eventually found WinClone V2.2 here.

You also need NTFSProgs so OS X can understand NTFS partitions. WinClone downloads them automatically, here is the link it uses.

Here's a screenshot of it in action:

WinClone Expanding windows file system

Go to Tools > Expand Windows file system.

Takes around 8 mins.

Worked. Cheers.

DeployStudio rc20 not showing new Disk Image Masters

I've just taken a Master image using DeployStudio but the image doesn't appear in the list of images, nor in the /Masters/HFS/ directory on the server. Of course this has happened before so I'm merely writing this down as reference.

The reason is because it uses a directory called /Masters/.workInProgress/ to store disk images whilst they're being made. When they are complete (which is after post processing like ASR scan and gzip) they get moved into the appropriate folder, in this case /Masters/HFS/. I think something happened and it never got moved. In the terminal I simply typed:

admin$ mv /Masters/.workInProgress/OSX-10_6_6-SMALL-2012-06-27.i386.hfs.dmg ../HFS/


But replace OSX-10_6_6-SMALL-2012-06-27.i386.hfs.dmg with the name of your disk image. Tab completion is the easiest way.

MacBook Pro Trackpad "not working properly" in Windows XP

Whenever I reimage MacBook Pro's with Windows XP I always have the same problem with the trackpad.

When you boot up, the trackpad does not function. Logging in and going to device manager you see that there is an exclamation mark over the trackpad. It simply says something like:

This device is not working properly. Error 16

Uninstalling, reinstalling, disabling, enabling does not fix it.

I reinstalled Bootcamp 3.0 drivers which did not help.

I found this forum quite interesting. Seems to mention about uninstalling some Windows Apple things in "Add/Remove Programs". But I didn't try this.

I next updated to Bootcamp 3.1 drivers and rebooted. Worked a treat!


.............
Update - 24/09/2012

Well, just reimaged a macbook pro and the same problem occurred. Installed Bootcamp 3.1 and it didn't work!

Finally had a look at the forum mentioned above and the solution they gave worked. More specifically:

1. go to Device Manager and update the driver for the trackpad.
2. click "No, not this time" for internet update.
3. Click, "install from a list or specific location".
4. click, "Don't search, I will choose a driver to install"
5. Choose the generic driver.
6. Click finish

The trackpad starts to work but no multitouch facilities. This is the point you install/reinstall bootcamp 3 and 3.1.

After this it works a treat.

Deploy Studio RC20 MultiCasting on OS X 10.4.11 xserver

After finally finishing the Master image it came in at 72GB! Takes about 3 hours to image one machine and 6 hours for two. So I thought I'd give Multicasting another go (I tried it a couple of years ago with lots of lost packets!). Also just heard they refitted the server room so maybe this'll help.

It was set up a few months back when we had DHCP problems caused by upgrading DeployStudio to RC20. You get the option to set up Multicasting when you set up DeployStudio Server. Here's my post

So taking a new iMac 24" and an old white 21" iMac I thought I'd set up Multicasting. First in DeployStudio admin I clicked the image and clicked the Multicast button at the bottom (looks like the Airport icon)

Airport Icon at bottom denotes MultiCasting

This now shows it's multicasting in the Activity section.

I've set up a workflow to restore an image to a volume, and in this set up some Multicast options.

Setting up Multicast options in a workflow

So far I have tried:

• Attempt 1
• Stream Rate 6MB/s
• Clients Disk Speed 120MB/s (I wasn't sure about the older 21" iMac so I slowed it from 200MB/s)
• Start Trigger 2 client
• Result:
• Stream Rate 5MB/s
• Disk Rate changes from 5MB/s to 15MB/s

I've been writing this as the process is going, and just noticed at 12:48 that some errors occurred. I noticed that this happened around the time that I loaded DeployStudio Admin on my machine, so I think this might have caused a slight interruption on the server (and it is 7 years old now). I do remember that I once remote'd into a machine whilst imaging which interrupted it. So the process is a little delicate. I shall wait to see if it has effected the process or whether it can cope with a few byte missing here and there?

After waiting until the 100% marker (which took 3 hours) it seemed to have stopped with no more errors, although it didn't quite finish. It said something about "starting" but just stopped there. I waited for another hour with no more progress so decided to reboot. Upon reboot the startup disk was not set, and the came up with the white screen with a question mark!

My initial conclusion was that the process had failed, but in hindsight I think that maybe the computers were waiting the data that was lost to be broadcast again, but this might be me clutching at straws. I shall look into it at the end of August. For now we'll just have the old method to use.

Imaging OS X 10.6.6 on OS X server 10.4.11

I have over 100 Macs which need reimaging this summer. To make it nice and simple they will all have 10.6.6 installed. Unfortunately I only have a 10.4.11 server (PPC) which I don't think will be upgraded before summer ends! At the moment I have 9 brand new 27" iMacs which don't like the current version of Deploy Studio RC20.

The reason I only have RC20 installed it that this was the last version to support OS X 10.4.11. Now, I also have 9 24" new'ish iMacs which do work with Deploy Studio RC20, and some relatively new Mac Pro's which definitely work with Deploy Studio RC20. So it is still worth perhaps using it for the 90 or so Macs and resort to other techniques to reimage the 9 which don't work. Of course over time I will need a new system but to have a really good new system we'll need time.

So the plan is to carry on using deploy studio for 90% of the Macs, and resort to something else for the last 10%. Alternatives are:

• Carbon Copy Cloner
• SuperDuper
• The install disk
• the install disk on a removable hard drive
• A bootable 10.6.6 on a removable hard drive

Well, I've looked up CCC and can't find any reference to it having some bootable interface. It simply copies a hard drive to another, which to be fair could be bootable, so I might do this.

I'm currently trying the easiest of these which is to use the install disk. I've managed to find the command line for mounting an AFP share. So I've open terminal from the booted up install disk and typed:

mkdir /Volumes/tmp
mount -t afp afp://username:password@server.somewhere.ac.uk/Images/ /Volumes/tmp/

The image that was taken from the 10.6.6 27" iMac was either done in DeployStudio helper or Disk Utility. When trying to restore this image to a drive in Disk Utility it has come up with an error message:

Restore Failure Could not find any scan information. The source image needs to be imagescanned/scanned for restore

I did a quick search and came up with this. I do now remember that to restore off a network share using disk utility it does need to be scanned for restore. Put the image in Disk Utility and go to: Image > Scan for Restore. This takes a long time on the old Apple Server G4, but not so long on the new 27" iMacs!

It should be ready for restore now...

Restored 70GB compressed in 1 hour 45 over the old network, which isn't too bad. I don't think it'll be able to do multiple machines very efficiently though.

The next process is to try and create or use an old netboot image to netboot the slightly older machines. So it only gets easier from this moment onwards.

Setting up the new 27" iMacs

Setup started with the simple "hold down the n button" to netboot/netinstall. The first problem was that the current netinstall image would not work on the new iMacs, doh! So I set about making a new one. The old deploy studio RC20 seems to crash whilst making an image, so I needed to use a newer one. This newer one imaged without crashing, but when netbooting came up with a message saying the server needed updating to cope with the new netboot image.

The next thing I tried was to put an iMac in target disk mode and just reimage it using a 24" imac with I know works. I put the Mac Pro 10.6.6 image on it but would not boot up. This was probably due to new drivers not being on the image!

My last attempt is to start from scratch (or nearly from scratch) and install everything. I updated the operating system to the latest 10.6.8. I took a shortcut though and used "Migration Assistant" to pull across applications from the 10.6.6 image. This worked and only required me to install the newest of things. Heres a list of things which is now on the new iMac:

• Adobe CS5
• Final Cut Studio
• Firefox 4
• Acrobat 9 Pro
• Papercut client
• Celtx
• Office 2008 (required rosetta)
• Handbrake

And drivers

• Scanwizard
• Dell 3110 driver
• Pixma Driver
• Konica Driver
• HP Scanner 4370
• Wacom tablet
• Flip4Mac

After all this I tried a students account. It required 2 login attempts to get me in though. I then tried all the apps. The problems I encountered were:

• Photoshop crash on launch
• Illustrator crash on launch
• Indesign crash on launch
• Acrobat crash on launch

These were probably due to NHR (network home relocation) script not installed. I installed it and Photoshop and Acrobat started working. Unfortunately Illustrator nor InDesign would work! They worked perfectly fine on a local login. I ran the CS5 install again, and also updated Illustrator to 15.0.2 and InDesign to 7.0.4. Illustrator would crash on load up, and indesign would crash on the "new document" screen which comes up first. My only clue was a message which popped up in console which I can't quite remember now. Something to do with transport2app error 255.

Just relogged in and tried it again. The error's I'm getting from the console are:

07/07/2011 14:01:43 kernel smbfs_vnop_link: warning: pid 665(Adobe Illustrato) hardlink(~v3vZO_cBdNvr4jqB)

07/07/2011 14:01:49 mdworker32[673] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

07/07/2011 14:01:51 mdworker[658] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.

The first refers to the smbfs (samba file system) which must be the home drive of the student which is hosted on a windows share.

The only real difference is that the operating system in 10.6.8 instead of 10.6.6. I think I will have to redo this on a 10.6.6 machine....

So, redone a 10.6.6 version and migrated everything from 10.6.8 iMac. Everything worked! (apart from Adobe Acrobat and Dreamweaver. Acrobat crashes and dreamweaver gets stuck even loading up. I installed NHR and still the same. Interestingly Illustrator worked without NHR!

Looking into the issue a little more, I found that NHR is not entirely working. I've noticed that the caches folder is not being relocated, although the fonts folder is? I will have to look into this further. At the time I thought this was due to the test account having the links set up already from another machine, but thinking about it now these links should be deleted on logout! So now I'm thinking about it, it was originally working and now somehow it is not working any longer.

Deploy Studio Set up RC20

So after my trials and tribulations with Deploy Studio RC20 we ended up uninstalling it completely so as to rule it out. But alas, it was needed and so upon reinstalling it, I found that I needed to set it up again. So refering back to my notes........ doh, didn't make many notes (in fact I only made one note), and so I am writing this 'note' on how I did it.

So, I worked out that you need to start the service before setting it up. It's because it gives itself it's name based on the server address, and does other things. So, after this I refered to the pdf I downloaded, which is a little out of date and NOT made by the people who made Deploy Studio (I have no idea why?). So basically:

This network sharepoint was setup previously

These groups were also setup previously

These settings are the default settings and haven't been tested. It did state in the PDF that the IP address should be that of the server, but this is incorrect. It has to do with multicasting.

So, hopefully this helps in the future. Let it be known that I have taken notes!

Deploy Studio set up and DHCP problems

I've been using Deploy Studio server for at least 1 year, perhaps 2, and it's fantastic. It's streamlined imaging perfectly, with workflows helping with different setups.

But all good things have their drawbacks, and upon upgrading Deploy Studio server from RC14 to RC20 everything appeared good, until two days later the Network Administrator rings me up and asks if he can unplug the Xserver, doh! It appeared to be the cause of much dismay for those two days, constantly giving all computers wrong DHCP information, for which is was not even meant to be giving!

We looked into it and the Xserver was responding to DHCP requests and giving "no-dns-server.example.com" as the dns server, overriding what the computers normally had set, which caused much much confusion. It was of course quite amazing that the network administrator managed to track it down to this problem, but I do suppose it took two days.

Upon closer examination, we noticed the DHCP service was "apparently" not running, but when we switched the "Netboot' service off it no longer responded to DHCP requests. So it was the Netboot service which was using part of the DHCP service, which Alan was sure was not 'usual'. Of course we were not sure what it did before the trouble started, whether or not it responded before of not, and whether it was just the fact it was dishing out the wrong DHCP information (IP Stack someone later told me) rather then no information.

We looked at the stopped DHCP service settings and saw one entry, which did have "no-dns-server.example.com" in it's properties. We deleted this entry, which was the only entry, but we still received responses. We measured these responses and it was now giving out the right information, which was better, but we would have preferred it not to give any information.

So to conclude, I whittled it down to the update from Deploy Studio RC14 to RC20, where Deploy Studio had changed, and perhaps added the "no-dns-server.example.com" entry the way Netboot used the  DHCP service.

iMac 21.5" - 11, 2 - 10.6.6 - Installation and deployment - Part 2

After NetInstalling OS X 10.5.8 on the new iMac I got a black screen. I still think it was worth a try.

So, I swapped the "fully updated" one for another new iMac so I could start at OS X 10.6.4. Tried Active Directory and it worked fine, as well as NHR login scripts. So I jumped to the conclusion that it was in the use of "Migration Assistant" that some 'damage' occurred. But, I was still cautious of updating the operating system any further. My plan is/was to update everything else, image it, then update the operating system to see if everything still works and carry on accordingly.

So, I had to start from scratch and installed:

• Final Cut Studio 2 - had to install at least 3 times to get 'all' the files
• Aperture
• Adobe CS5
• Adobe Acrobat Pro 9 - no serial number
• CeltX
• Audacity
• iWork 09
• Burn
• ClickView
• DivX
• Firefox 3.6.13
• Handbrake
• Office 2008
• Mplayer Ex...
• DeployStudio RC20
• NHRBasic
• Flip4Mac
• ARD Client 3.4
• PCclient
• Don't have "Logic" Disks on server
• VLC 1.1.7

Scanners:

• HP Scanjet 4370
• Nikon CoolScan 8000
• Scanwizard Pro 7.20

Printers:

• 5550
• 3110
• Canon Pixma IP4500
• Konica 7300

Tablets:

• PenTablet 521-3 - I think this covers all the tablets we have.

Forgot also to add "Media" user to the local users.

I partitioned the HD via Boot Camp Assistant and formatted it as HFS+ Journaled, named "Scratch Disk". Just going to make the first image now.....

.... and now just updated to 10.6.6, and student login worked just fine! So to conclude, "Migration Assistant" probably isn't good for transferring apps across operating system versions.

I am now imaging using Deploy Studio, but having to clear a bit of space on the server so it can fit on. The space taken on the iMac is 85GB, it needed more then 130GB (not sure how much more) for doing server side compression, I've now freed up 200GB on the server. 78 mins till it's uploaded, but then it'll take the old server, bless the poor thing, quite a while to compress the image.

... I left it over night and it did it. A nice thing to note is that if you use a local repository, I think it doesn't use the server to compress the image.

Worked a charm, and even worked with multicasting, yay.

iMac 21.5" - 11, 2 - 10.6.6 - Installation and deployment

Just received 10 new 21.5" iMacs, version "11, 2" ,  with 10.6.6 installed. Very nice, with quad core and 1GB Hard Drives, but having a few different issues has caused me to put them back to 10.5.8 temporarily until the main issues are fixed.

To streamline the operation I decided rather then starting from scratch, I would use Migration Assistant to transfer accounts and applications from the latest MacBook Pro which had everything on. This worked very well, but in heinsight might have caused the issues below. These problems need testing on a fresh install of OS X 10.6.6.

Issues which I encountered:

• Students on Active Directory require to put details in more then once before they can login, for machines only just switched on!! I think this is to do with how quick the mac boots up, too quick to authenticate itself on active directory?
• NHR (Network Home Redirector) scripts not running at login or logout.
• Deploy Studio netboot not working; firstly freezing on the white screen with the grey apple (no spinning wheel, and secondly crashing and rebooting when loading the next screen after the one just mentioned.

With the students active directory issue (not properly tested on staff accounts), there was not much to try as I think it is more of a problem with Active Directory Servers or how OS X 10.6.6 communicates with them, which is too time consuming at present (there is pressure to deploy iMacs within the next 2 days at most). I did some simply exploratory fixes:

1. take off of active directory and put it back on
2. make sure everything was up-to-date
3. refer back to solution 1.

When there is more time I shall need to look into this, but also future releases of the operating system will fix these. One thing I would like to do is try active directory logins on a fresh install of the operating system

With NHR I downloaded the latest, 3.2.6, uninstalled and reinstalled. What might have caused the problems is that I transferred files from a MacBook Pro running 10.5.8, which might have transferred some of NHR Scripts but not all. I also tried the full version which creates more alias's. Unfortunately not much info on NHR website, no-one else seems to be having problems. One thing I would like to do is try the scripts on a fresh copy of 10.6.6.

After these two problems and diminishing time I decided it was best to revert to 10.5.8 until time would allow these problems to be resolved. But, I did not want my efforts to go to waste, so I decided to make a disk image of the machine with its' problems so I can continue later. Little was I to suspect any more issues. I held down 'N' for netboot to DeployStudio and the machine froze on the white screen with the grey apple (no spinning wheel). Doh! The problem was probably because the last deploy studio netboot image was made on a MacBook Pro 15" now 2 years old.

I subsequently made a new netboot image (nbi) from this iMac and tried again, this time to get the spinning wheel but to crash on trying to load the next screen! This was probably due to outdated DeployStudio (currently using RC14 on the server and RC 15 on clients). I updated the client to the latest and the same happened again! So I updated the server, but alas, the installer said the minimum requirements were not met!! Server is running 10.4.11!!! Needs updating!!! So I go traipsing around for the last version to support 10.4.11 server, which was a lot of hassle. I'd like to not that the DeployStudio website (both Wiki and main site) are not good for troubleshooting, with only the latest versions available. I finally found RC20 here. Eventually worked! Yay.

After this I went to make an image of the drive but alas, not enough room on the server. So I used Boot Camp Assistant in OS X 10.6.6, and partitioned the drive - 160GB for OS X and the rest for "Scratch Disk". I then NetBooted again and used Disk Utility to make a compressed Disk Image and put it on the Scratch. Turned out to be 79GB, original was 106GB.

So now to put OS X 10.5.8 on, which will hopefully work on this machine!!