Tag Archives: Deployment

Software – Finale Silent Install on windows

To install Finale silently use …
FinWinSetup.exe /S

Also – it appears that copying in a “keyed” (keyServer environment) executable also “authorizes” the application on Windows without having to enter the authorization code. Therefore, to deploy this I need a batch script which executes the installer silently and then copies in the keyed copy.

For a partial reference see:


http://makemusic.custhelp.com/app/answers/detail/a_id/945/

Dec 2011 – Imaging Log

Imaging with the Winter/Spring 2012 image on all computers in the following spaces is complete … Exceptions noted with issues listed at the end ….

Labs:

  • Bronfman 119
  • Harper GIS
  • Jesup B03
  • Jesup 101
  • Jesup 204
  • Jesup 207
  • Jesup 316a
  • Schow GIS

Lecterns:
(Individual computers in parenthesis need to be checked and/or imaged – see complete list of computers with issues below.)

  • Bernhard
  • Bronfman
  • Clark (Clk-105-pc not set to boot to network)
  • Griffin (gfn-002-mac needs to be checked)
  • Greylock (Greylock D – mac and pc are unresponsive and are likely “broken”)
  • Hollander (nab-040-pc not set to boot to network)
  • Hopkins (names change)
  • Jesup (jsp-205-pc to be replaced with dual-boot, jsp-206-pc not set to boot to network)
  • Lawrence
  • Paresky
  • Schapiro (sab-137-pc not set to boot to network)
  • TBL – Biology
  • TCL – Chemistry (tcl-206-pc not set to boot to network first)
  • TPL – Physics
  • Weston

Libraries:

  • Sawyer Classroom (swy-cls-03 not set to boot each morning)
  • Sawyer Lower Level Lab
  • Sawyer Main level (swy-bay-1 and swy-opn-28 need to be checked)
  • Schow Atrium (ssl-atrium-14 and ssl-atrium-24 not set to boot each morning)
  • Schow Classroom

Specific computers with issues:

These are likely unusable:

  • glk-d-mac and glk-d-pc — image process did not complete correctly, reboot to restart imaging process
  • swy-bay-01 and swy-opn-28 — image process did not complete correctly, reboot to restart imaging process

These are likely usable but will need to be checked and imaged in January:

  • clk-105-pc — not set to boot to network first
  • ctd-sem-pc — not on-line
  • gfn-002-mac — not on-line
  • jsp-206-pc — not set to boot to network first
  • nab-040-pc — not set to boot to network first
  • sab-137-pc — not set to boot to network first
  • spn-212-pc — not on-line
  • ssl-atrium-14 and ssl-atrium-24 — not set to boot each morning
  • swy-cls-03 — not set to boot each morning
  • tcl-206-pc — not set to boot to network first

Still to do:

  • CDE Lectern and lab – not till after winter study
  • Clark lab
  • ’62 CTD lectern and lab
  • Jesup 205 – not till January, photography image
  • Jesup 316 (3 of 7 still need to do)
  • Spencer lectern and labs
  • Physics lab (not till January)

Mac – DeployStudio and AD join

Deploying a Mac OS image and adding the computer to the AD can all be accomplished using DeployStudio. I suggest that you set up your AD environment to use “OUs” (organizational units) for your computers rather than have them all in the one default “computers” OU. I have two production OUs of “Labs” and “Labs-Macs”. I’ll explain the “Labs” OU structure for windows in a different post …. For now, just add computer accounts for all your macs to an OU. The computer accounts should match exactly the host names you are using just like you would do for windows.

Then in DeployStudio –
Add the computers and set their “Local Hostname” and “Computer Name” to the same thing you entered in the AD for their computer accounts. Your workflow for the deployment should include a step to rename the mac and after that step the AD binding. In that AD binding window be sure to set the fields for the domain to join and the computers node. Here is a screen shot of my set-up …

Mac – DeployStudio and windows volume

When creating a workflow for taking a DeployStudio image of a windows NTFS volume — it is important to uncheck the box for use “mac tools for multicast” which then allows you to check the box for “try to shrink the NTFS volume before taking image”. If you do not shrink the volume the imaging process will fail with an error about not being able to change the partition size.

Watch for this setting since it can revert back to the default “multicast” setting, which does not work, when you upgrade the DeployStudio software

For more details see:
http://deploystudio.wikispaces.com/Creating+a+NTFS+Master+Image+on+Bootcamp+2.x

Windows 7 – Allow Remote Desktop

Remote desktop access is not allowed by default in Windows 7. I change this both in the image before deployment and I also set this in group policy. if I just do this in group policy, I will be prevented from connecting to a deployed computer that has had a problem with renaming and/or joining the domain …

To allow access into a windows 7 computer from a non-windows 7 computer be sure to set … “Select Allow Connections From Computers Running Any Version Of Remote Desktop to allow connections from any version of Windows.”

For details on allowing remote desktop access see:
http://technet.microsoft.com/en-us/magazine/ff404238.aspx