Setting all Apple Macs to use network time servers

So I wanted to change all the Macs here to use our specific network time servers so that their time is never out and so cause login issues. I did it by first finding the command line arguments, then making a shell script, then making a pkg file which the OS X task server sent to all the machines when they are powered on.

Here's the step by step guide:

1. finding the command line arguments:
1. sudo systemsetup -setnetworktimeserver your.time.server.ac.uk
2. sudo systemsetup -setusingnetworktime on
2. making a shell script
1. make a new plain text document using "TextEdit"
2. make the first line:
1. #!/bin/bash
3. paste the two lines from 1.1 and 1.2
4. save as (untick "add .txt file extension) and put .sh at the end
5. make it executable
1. in terminal type:
1. chmod 744 nameOfShellScript.sh
3. make a .pkg file which runs this script
1. I use Iceberg. Here are the screenshots:








2. When done, go to Build > build
3. navigate to the project folder in Finder and inside the "Build" folder you'll find the .pkg file.
4. test it on a computer
5. Send to all machine
1. I use Apple Remote Desktop Task Server for this

1. select the computers in a list
2. click "Install Packages"
3. select the package
4. select "run this task from: The Task Server on your.task.server.ac.uk"
5. sorted
2. sorted
6. sorted

sendLogon.app and installer

Well, after much troubles over getting NHR to also run sendLogon on startup, I decided to just make an application which ran the sendLogon script:

/usr/bin/sendLogon 145.xxx.xxx.xxx 5438 $(logname)

1. I simply made it in Automator:
1. 
2. Next I made an installation package to install it along with the sendLogon command program

I used Apple Remote Desktop's "Task Server" to install it on all managed machines. And finally I used Workgroup Manager to have it as a Login Item on the managed machines.

I think it works out better this way, as there is a little bit more control over it.

OS X multiple login scripts - sendlogon and NHR

So, after having NHR running for quite a while, it looks like we also need to have sendlogon running at login. This isn't the first time I've had to have multiple login scripts. I remember doing this for BootPicker back when it wasn't included in the operating system.

So to do this I will use the system already in place thanks to NHR. At the moment, at login, the file /etc/login.hook runs. This runs any scripts within the /etc/hooks folder which begin with "Li". The same thing happens for logout but with any files beginning with "Lo". So, all I have to do is to rename the "login.sh" script something like "Lisendlogon.hook" and it will run at login.

Now, this "lisendlogon.hook" script simply contains the command to run the "sendlogon" program plus the right syntax to put after it. i.e. the server and the current users credentials. This is how it looks:

#!/bin/tcsh

/usr/bin/sendLogon dns.name.of.server.com 3898 $1

The sendLogon is in the /usr/bin folder, as this is where their tutorial says it should be.


After testing this, I need to make an install pkg file to run from the task server. I like using IceBerg.


So, here's some screenshots from it:

Iceberg - fix NHR and sendlogon settings page

postflight installation scripts.

writeloginhook.sh contains:

#!/bin/tcsh

sudo defaults write com.apple.loginwindow LoginHook /etc/login.hook

which tells the operating system to run /etc/login.hook at login. 

iceberg - files section. Later found the default destination needs to be "/"

I got slightly confused as to which folder to make the default destination?

I'll test it out on a computer suite machine to see if it works.

After a little testing, it looks like it didn't put sendLogon into /usr/bin! After trying a few things it turns out it was down to the "Default Destination". After setting this as "/" it worked. It looks like this is basically the folder which all installation folders have in common.

Iceberg - files section with the correct "default destination" as the lowest common folder.

Tested and works fine.

Cheers

Deleting all print queues on OS X using Command Line

So, here's a little script which deletes all the print queues on OS X. I run it through Apple Remote Desktop's "Send Unix Command" as root:


for printer in `lpstat -a | awk '{print $1}'`
do
echo Deleting $printer
lpadmin -x $printer
done

We're moving our print server to a UniFLOW system and so I need to get rid of all the print queues and add new ones (adding them through Workgroup Manager).

Thought I'd make a little pkg file which I can send to all machines through ARD Task Server. I did it through Iceberg. Here's a few screen shots of it with notes:

Adding a preflight script to run

This is the script which runs on preflight

Simple really, but works.

Deploying Canon EOS 230M stuff on Mac OS X using Iceberg

So we have some lovely HD SL Cameras from Canon. Some sort of EOS model. Very nice. It comes with some software which you need to use these cameras with OS X. Unfortunately Canon neglected to use Apples standard package installer concept and made there own (or bought one it). So I've now got to find a way to put this software on all the machines.

There are two simple ways:

1. would be to simply copy these applications to other computers.
2. Would be to utilise the "Record" facility in the Application "Package Maker" which would hopefully record the files and scripts that the Canon install program performed. (Can't find a copy of Package Maker though!)

Having tried number 1. it looks like it's worked alright. So next is to make a pkg file which puts these apps in the Applications folder. I shall refer to a previous post here how I made a pkg file which installed "fix everything please" and sendlogon.

So, here's how I did it:

1. I used a free Application called Iceberg
2. Made a new project and created a nice little folder for the project
3. Entered the standard details for the Settings

1. I put Admin Authorisation so there would be some control
4. Skipped through the other sections to get to the Files section

1. I made /Applications the Default Destination
2. In Applications I right clicked and selected "Add Files..."
3. I selected the folder which was in my Applications folder on the computer (I'd installed it earlier)
4. I noticed that it didn't show the folders inside the "Canon Utilities". I was just about to click the "Add files..." option again but I did see an option to "Expand All". I clicked it and what do you know, it updated the folder to have all the subfolders it should have had!
5. Next I clicked "Build" and it was done.

Just doing testing at the moment...

Yep, works like a dream!

Making a pkg file for installing sendLogon for Bloxx on OS X

In a previous post I described how we're getting a new web filtering system called Bloxx, which needs the sendLogon program to be installed and run as a login script on all the Apple Macs (OS X).

I used Iceberg free application to make the PKG file as I've used it before with relative ease, and also couldn't find the latest official Apple PKG maker app!!

Its all working now so here's how I did it:

1. Made a new project in Iceburg, and made a nice little folder to hold all the files needed (makes it easier to find things)
2. I filled in the top section "Settings"

3. Next was the "Scripts" section. I had to make a script which changed the com.apple.loginwindow plist file to add the LoginHook /usr/bin/login.sh
1. I ran nano from the command line (nano ~Desktop/sendLogonfiles/Install\ sendLogon/writeloginhook.sh)
    and typed:
2.  #!/bin/tcsh
   sudo defaults write com.apple.loginwindow LoginHook /usr/bin/login.sh
3. I found I had to put "sudo" into the script so that it had the right permissions to write to the file. Not sure why else it didn't work?
4. I saved the file and made the file executable - chmod 755 ~Desktop/sendLogonfiles/Install\ sendLogon/writeloginhook.sh
4. I then added this script to the "PostFlight" script, and set the path to "Relative". Note - I found an article here documenting the definition of each of these types of scripts. Most were concerned with whether this was an upgrade or not, and would only run once.

5. Finally was the "Files" section. 

1. I firstly put the files in the project folder.
2. I set these files with the correct permissions (as in the tutorial folder for sendLogon). chmod 755
3. Then, in Iceberg, I had to add the folders; /usr/ and /usr/bin/, which were not there.
4. I then made the "Default Destination" the /usr/bin/ folder
5. Finally I added the login.sh file and the sendLogon file.

I've just tested this through the Apple Remote Desktop Task Server on a single MacBook Pro and worked a charm (had to ring ICT though to add its' IP address to the Bloxx list of computers with sendLogon working)

Note: There is potential also for adding to this a little script which changes the proxy settings to the system and maybe also Firefox, but it would be easier to control these settings through a .pac file or .wpad file.

Making a pkg file to distribute through ARD Task Server

After making my little "Fix Everything Please" Automator Application I wanted to distribute it to all the machines, and the easiest way of doing this is using the much unused Task Server I have set up through Apple Remote Desktop. I have done this process before, but not documented it very well. What's worse is that I cannot find the newest "PackageMaker" application since re-imaging my machine, only the one which comes with Remote Desktop, which was originally for OS X 10.4! Apparently you can download it with the newest iPhone SDK which comes with XCode.

So, after some looking I found a well reviewed Package Maker app called Iceburg. Downloaded it, installed it and rebooted. Apparently it's a lot simpler then PackageMaker and I'd made the package in about 3 minutes. This is how I did it:

1. Make a "New Project"
2. Fill in the "Settings" section:



Settings section of Iceburg Package Maker

1. I put Admin Authorisation so there would be some control
3. Fill in the Files section at the bottom:
1. I clicked on Applications and pressed the "Set" button to set this as the Directory it was going



Files section of Iceburg Package Maker

2. I right clicked on the Applications folder and chose "Add Files..." and chose "Fix Everything Please.app" (I made sure the permissions were right in Finder before I did this)
4. Clicked "Build and Run" in the top menus

Worked a charm. I had a little trouble getting the permissions right. At first it would make it "Read Write" for "Everyone". I changed the permissions and then re-added it to Iceburg and it seemed to work.