And the compatibility issues with third-party software and hardware device drivers have largely been ironed away; after all, it's been two and a half years since Vista debuted. Windows 7 even includes a virtual "XP mode" for running legacy programs. Find out what's new, what's wrong, and what's good about Windows 7 in InfoWorld's " Windows 7: The essential guide. Windows 7 goes a few steps beyond merely repairing Vista. It borrows --and improves on -- tricks from the Mac's playbook to make it easier and faster to organize files and launch programs.
Like Apple's operating system, Windows 7 not only looks good, but it has tools and shortcuts that help you work more efficiently. Still, once you've had Mac, can you ever go back? Although the changes to the GUI are minimal why mess with success?
After spending a few weeks with both new operating systems and exposing each to my geek's gauntlet of everyday tasks -- e-mail, instant messaging, Web surfing, blogging, creating and editing Office documents, Web page creation, and audio, video, and photo editing -- I have to call Snow Leopard the winner.
If you are deploying Windows Vista please see the step-by-step Windows Vista Sysprep guide found on this page: For older deploystduio simply download it from here… http: Winclone will automatically expand the image to fill the destination partition.
Delivered Daily Subscribe Best of the Week Our editors highlight the TechRepublic articles, galleries, and videos that you absolutely cannot miss to stay current on the latest IT news, innovations, and tips. They must also be deployed to the same size partition. This may be useful if all you want to do is specify a workflow and add a script on the end. DeployStudio, NetBoot and the various workflows can, and in many cases are intended to, erase all data on remote systems.
If your network is slow and local drive-to-drive copies would be faster. Following a deployment it may be desirable to shutdown the system as opposed to the default configuration, which is to reboot the system.
Click Continue The drive will now allow systems to start up using the DeployStudio Runtime, very similar to NetBoot images discussed earlier in this guide. Otherwise no restart default or shutdown will be exercised. Scan to E-mail Setup. More information about this capability may be found by visiting http: Set a computer to run a unicast deployment workflow and NetBoot that computer b.
This is required e. Includes also an activity viewer to follow the status of the computers running DeployStudio Runtime. Build the image using Winclone a. If no data is provided in the default values found in the msnual database the user will be prompted to enter the information for each system upon deployment.
Windows NTFS images cannot be broadcast using multicast. Create any users ie an admin account for remote administration and an Apple Remote Desktop user account.
Whats new in this guide Updated: Sunday, January 9, Version 2. This guide also includes information on deploying Windows 7 images. Overview Please note: this guide is intended to be a resource for building and deploying images using DeployStudio. The author assumes no responsibility for lost time or lost data when using the tools described in this guide.
DeployStudio is intended to partition and re-image systems and, when congured as such, will erase all data on the drive. It is important to understand this capability as it can cause automated, unrecoverable data erasure, depending on the chosen, congured deployment. The author of this guide has no afliation with the developers of DeployStudio.
Thirdparty company and product names mentioned herein are trademarks of their respective companies. Mention of third-party products is for information purposes only and constitutes neither an endorsement nor a recommendation to use those products.
The author assumes no responsibility with regard to the performance of these products. It is recommended you rst search for the issue youre experiencing.
If you cannot nd the answer youre looking for, post the question to the forum. While current versions of DeployStudio support running either Differences in both interface and functionality between Leopard Server and Snow Leopard Server will not be pointed out.
DeployStudio has established itself as the premier, free tool for creating, customizing and deploying images. Initially, you may nd all the features of DeployStudio a bit overwhelming. However, it is a comprehensive well-thought out solution for customizing and deploying images either locally or across the network.
DeployStudio can assist in the creation of single, dual and triple boot Macintosh systems. DeployStudio can also be congured to run locally from a hard drive.
This guide will concentrate on setting up a private network based deployment of images to multiple machines simultaneously. DeployStudio documentation is sparse, which is the motivation for creating this guide. At this time, this guide will not discuss PXE booting. This guide will step through setting up Mac OS X Server, installing and conguring DeployStudio, creating images for deployment and deploying and customizing images.
It is important to rst have a general understanding of the various components required. There are also a number of components in DeployStudio for building, managing and customizing deployment images. A summary of those services is as follows: Snow Leopard Server Components File sharing - AFP Apple File Protocol Retains a central repository for all DeployStudio computer records, workows, master images and scripts that are accessible from both the server and remotely from client systems for image creation and image deployment.
Only necessary if isolated from a main network e. DNS - Required for server services including le sharing, user creation and basic server functionality. NetBoot - Service for booting client systems from a network based image so that they can be completely erased and restored. Open Directory - Directory services used for user and group creation for le sharing and access to the DeployStudio repository and the DeployStudio web server.
Also a tool for creating PXE boot images. DeployStudio Admin - Central location for recent activities, managing computers and computer groups, creating workows, managing master images for deployment, managing packages and for maintaining scripts. Activity - Monitor systems while their workow is running. Verify each step completed successfully and view logs for each session.
Computers - each computer can have custom scripts and workows associated with it. It allows one to specify the hostname, new users, network settings, etc.
Similarly it can create computer groups for automating complete workows on multiple machines simultaneously. Workows - Create custom step-by-step workows for image creation, image deployment, partitioning, running scripts, installing packages, connecting to directory services, setting up various specic network settings, setting the rmware password, binding to directory servers and more.
Multiple workows can be created for a variety of deployments all managed by individual computers or computer groups. Workows may also be combined using the Meta Workow task. Masters - Manage the master images you have created for deployment so that they can easily be added to workows.
Scripts - Customize scripts for further system customization before or after deployment occurs. Packages - Install software packages including Mac OS X updates, Apple software or third party software that uses the. These may be added after the initial install for custom setups for different locations or to ease the creation process of the master image by supplementing new software releases or updates.
These installers may even be run post restart in the event certain software must be installed from the running OS drive or verify installed software like the iLife suite, which veries the version of QuickTime that is installed. DeployStudio Runtime - Tool for running the various Workows created in DeployStudio Admin including image creation, image deployment and running scripts for customization. This tool will present itself when the system NetBoots or can be run locally to create or deploy images from a local hard drive.
Chapter 1 - Introduction This guide is very specic in what it covers. By following this guide you will be able to deploy a Mac OS X While DeployStudio is a powerful and fairly intuitive tool, it does not offer full documentation or help les. Currently Future versions for the may only include support for Please see the DeployStudio web site for more information regarding DeployStudio Server compatibility. The following tools are necessary for a successful deployment: 1.
Mac OS X Server Server Admin - enabling various services. NetBoot - network based startup image hosting. DNS - a properly congured dns is required for server connectivity and services.
Open Directory - user database which stores user names, passwords and permissions to various resources b. Workgroup Manager - user creation for management and access. DeployStudio Server a. DeployStudio Server repository - folder for storing various components, images, package installers and scripts. DeployStudio Server daemon - service running on the server running DeployStudio services.
DeployStudio Admin - congure and edit workows, computers, scripts and disk images. DeployStudio Runtime - the engine that connects to the repository and runs the various, pre-congured workows on the client system s. Set up OS X Server Create users necessary for DeployStudio and image hosting 3.
Set up share points for image creation and deployment 4. Congure NetBoot 5. Create a Mac OS X partition and install all necessary software 6. Build and customize the images for mass deployment 8. Build a basic NetBoot image for network based start up and deployment 7! Dual Boot System Image Deployment. Manage Workows for system customization during deployment Start the clients from a network volume to pull images down to the local drive This can result in up to 2X deployment performance.
If only one server is available, separate drives for the NetBoot images and the AFP DeployStudio Repository share point will enhance performance compared with a single drive. While neither of these is required, deployment times can be reduced by implementing either of these methods. This guide will focus on a single server utilizing a single hard drive. If your server is going to be used on an organizations managed network you will want to make sure you have a fully qualied domain name and a static IP address set up on the the central DNS server prior to using the Mac OS X Server Setup Assistant Verify that the parent DNS server has been congured correctly by running nslookup or another tool from a client system other than the server.
For example, in Terminal. Then in Terminal. Set up the Server - setting up the server the rst time is straightforward, however, selecting the right options for a standalone scenario is important. Welcome - select the Region and click Continue. Keyboard - select the keyboard layout and click Continue. Transfer an Existing Server - select Set up a new server and click Continue. Register the server if this is a reinstall and the Setup Assistant is running locally on the server as opposed to remotely you may bypass the registration with a Command-Q.
Time Zone - select the proper time zone and click Continue. Administrator Account - enter the Name and Short Name for the server administrator and the password.
Note: For security purposes it is recommended a different user be created for the server administrator, the directory administrator and the DeployStudio administrator. Internet Gateway - if prompted to congure an Internet Gateway, do not do so.
Click Continue. Network - congure the network information. Change the Congure IPv4: to Manually. Enter private IP Address ie Provide the Subnet Mask ie Enter the Router address with the same address as the server ie Click Continue and choose Ignore to the error message stating The IP address and the router are the same.
Users and Groups - congure Manually. Connect to a Directory Server - do not connect and click Continue. Directory Services - do not set up an Open Directory master and click Continue j. Review - click Set Up.
Select the server in the left column listed as either an IP address, the DNS name or the localhost name. Choose Settings from the top, then select the Services tab. DeployStudio Guide v. Note: As mentioned earlier, Snow Leopard Server will automatically congure DNS if none is detected, as in the case of a private network.
It is therefore not necessary to enable the service. Choose Save. Another tactic is to omit the DNS address in System Preferences for the network setup until the DNS service is properly congured which should allow you to overcome the temporary unresponsiveness of the server. Note: Occasionally, network server admins do not like additional DNS servers on their network for security and conict reasons.
Check with the network administrator before enabling DNS, unless, of course, youre managing a private network with NO network uplink connection. Turn the triangle in the left hand column of Server Admin to see the enabled services. If using the examples in this guide, These instructions assume the server IP address is Select Subnets iii. If a subnet already exists, select it iv. Under Subnet Name: name it Private Network v.
Starting IP Address: Ending IP Address: Subnet Mask: Network Interface: Typically, en0 depending on which ethernet port is used by the server ix. Router: Lease Time: 1 hours. DNS Servers: Default Search Domain: example. Select the checkbox to enable the subnet xv.
Choose Save xvi. This includes clients starting up using NetBoot. Note: When connecting more than clients simultaneously, one should broaden the range of private addresses available to clients and change the subnet mask to reect the changes. The scope of this information is beyond what is covered in this guide. Conguring Open Directory is not required but is recommended. In Server Admin, select Open Directory ii. Select Settings iii. Choose Change. Enter a user name and password. It is required that this user name be something other than the server admin user name and password i.
Click Continue vii. Click Continue ix. Conrm the settings are correct x. Click Done. Select the AFP service from the left ii.
This will be enabled in a later step after a NetBoot image has been created using the DeployStudio Assistant. Workgroup Manager - Congure the users you will use for DeployStudio access.
Launch Workgroup Manager and authenticate with the Directory Administrator credentials created in the Open Directory step previously discussed not the Server Administrator credentials, which may be the default behavior.
Disregard the message New users may not have access to services, if presented. In Server Admin, select the server in the left column. Choose File Sharing from the top. Select Share Points to the right of Volumes. Click Save. With Public still selected, choose Browse then select New Folder. Type in DeployStudio. Select Create. This topic is beyond the steps covered by this guide.
Launch the installer and follow the steps to install the software. License Agreement - agree to the license agreement to continue. Note: This software is provided for free and takes no responsibility for the loss of data by either being miscongured or bugs in the software. Select a Destination - choose the hard drive you will be running DeployStudio from. Select Continue. Select Install. Enter the Administrator user name and password for the system. Select Close, when nished.
Upon rst launch you will be prompted with a warning DeployStudioServer is not running on this computer. Server connection - if the Server Address: DNS name is not pre-populated, enter the dns name of the server followed by ie.
Then enter the user name created earlier in Workgroup Manager as dsadmin and the password associated with that user. Then click Continue. Server role - DeployStudio supports the ability to have multiple DeployStudio Servers on the same network for load balancing. This is an advanced feature and typically only necessary when server administrators have a lot of systems to deploy simultaneously and want to centrally manage those systems across multiple departments, schools, or organizational units.
Most administrators will not use replicas. Leave the setting as a master and click Continue. Repository settings - choose a network sharepoint.
Enter the user name dsadmin created earlier , the password for that user and under Use sub-folder: enter DeployStudio.
WARNING: Enabling a mail server without the highest level of security can potentially allow hackers to use your server as a spam server. Network Security - select com. Selecting the Interface is dependent on the server hardware being used. Mac Pros and Xserves have multiple Ethernet Ports. Leave the port set to Do not select Reject unknown computers, unless you plan to import lists of computers including the MAC address of every system. User Groups - if you want to restrict access to various users within groups created in Workgroup Manager for restricting the setup, creation, management and deployment of the DeployStudio Assistant, Admin and Runtime applications add the groups here.
These groups will need to have been created in Workgroup Manager with their respective users in each group. Users in these groups may be changed at any time after setting up the group.
This is recommended for tighter control and security. Conguring the groups is not a requirement. Enable Multicast - enabling multicast is discussed in a later chapter.
Note: Changing any settings in this window will not enable multicast on your network. Note: If Multicast is desired, it is possible to run the DeployStudio Assistant to set up a DeployStudio Server at a later time, without effecting the server settings. Click Continue to update the server settings. When the process is complete click OK. Note: When using DeployStudio Admin, you may receive an error stating failed to mount or access the repository while attempting to connect to the server.
This may be caused by not choosing a network sharepoint during the DeployStudio Assistant. Server set up process. Be sure NOT to choose a local folder and select a network sharepoint when running the assistant.
If, for example, a new system ships between That is to say, you cannot take an older OS like Occasionally, depending on the timing of the OS update release, ROM information for a system that shipped with Later updates may be required.
If this is the case, a newer machine will fail to boot. This will be exhibited either by a kernel panic experienced by lines across the screen or an incomplete boot process. Some OS releases will not boot other systems until subsequent releases have been provided by Apple in the form of OS updates. If you have a problem with a system not NetBooting or a Master Image does not allow the system to boot, the OS release for that system is not capable of booting it.
Apple does not guarantee an OS release will boot all systems. The current build statement above still applies. It is a good idea, however, to build a new NetBoot set often accomplished in less than 10 minutes. This will ensure the latest drivers, scripts and xes are included in the NetBoot image. NetBoot sets as of rc should be able to be updated with any new installs of DeployStudio. Administrators may use a Similarly, DeployStudio can deploy Dont confuse this with the fact that, as of 1.
Note: General Settings - be sure to create a name for the NetBoot set that will help you recognize when it was created for future reference. Note: If you have multiple NetBoot sets, make sure you are not using the same Unique identier for more than one image. Including a name that warns users not to choose this startup disk is also recommended.
Service Discovery - choose Connect to a specic server and enter the secure server address. Be sure to add the https and the port , if not already entered.
Note: The Alternative server could be the DeployStudio replica. Authentication - specify the default log in user i. This may have license implications for the software included in the master image. If you dont wish to automate the process, do not include default login information. This will require that every NetBooted system be touched by an administrator entering a user name and password. An alternative security measure could be to disable NetBoot when deployments are not occurring. You can use the same or different password for the VNC password.
Note: Administrators may choose to not use VNC for security reasons. Typically, choosing the Display Runtime log window by default is a good troubleshooting technique.
The Quit Runtime automatically after 30 seconds of inactivity should be chosen for the purpose of assisting with automating the deployment process. Options - certain applications require Python i. When using a package deployment workow, one or both of these tools may be required. Simply check them to add them to the NetBoot image. If youre experiencing slow network throughput when deploying the images, it may also be helpful to enable Custom TCP stack settings.
Simply build a new NetBoot image with that item checked. In most cases wireless, is not necessary on the NetBoot image. If the NetBootSP0 directory doesnt exist yet, it will automatically be created.
The NetBoot creation process will take several minutes. In the meantime, you will see a pinwheel informing you its working. DeployStudio NetBoot set created! Click OK. When the process is complete, the NetBoot service must be enabled in Server Admin to take advantage of the new NetBoot image. Launch Server Admin and authenticate, if necessary.
Select NetBoot. Check Ethernet. Choose the Images and Client Data locations depending on how many systems you will be imaging at a time, make sure you have plenty of free hard drive space on the volume you choose. Often this is a minimum of 2GB per system NetBooting. Select Save. Note: Be sure to Save this step, otherwise the image will not appear in the next step. Choose the Images tab - verify the image you created is visible and choose Default.
Customization can be as simple as creating an updated OS and software installations for deployment. It can also be as complex as customizing the image to authenticate to directory services, include multiple users and a customized user environment, replacing items, hiding users, etc.
There are a few things that are very important. Several of those steps are covered in this section. Make sure that all Macintosh hardware firmware and SMC is up to date. This process can not be completely automated due to the requirement of holding down the power button on each machine to activate the firmware or SMC updates. Install Mac OS X unless you are installing from a machine just out of the box, in which case you may want to use that default OS, as described earlier.
Note: Depending on the system you are creating, your master image from it may have software included that is only offered, and therefore licensed, for that particular model. Make sure you have a license for all software you are deploying. Install all updates to the OS and any installed software. Enable Apple Remote Desktop, if desired. Create any users i. Install and run all software once to verify serial numbers and build font lists. The following applications may be useful, depending on the type of deployment: i.
Flip4Mac - allows users to play Windows Media Files ii. Apple Remote Desktop - update to the current client version iii. Boot Picker - install the latest version iv.
Deep Freeze - obtain a license, install and configure. Any Virus software deployed in the off setting h. Enabling and disabling various functions may also be helpful or necessary: i. Disable remote control infrared receiver. If you bound the system for testing Active Directory or Open Directory testing, you must unbind the system prior to creating the image. There are several additional Mac OS X customization options you may want to take advantage of.
In a scenario where DeployStudio is not used, each imaged machine is using the same security certificate and hash. Deploying a single image will deploy the same LKDC to every system.
It is for this reason that images should be built and deployed using DeployStudio Workflows. Disk Utility is one example of a tool that will not properly build an image to successfully manage the LKDC deletion and re-creation. The method for creating a master Windows XP partition compared with a Windows 7 master image in regards to SysPrep is different.
This chapter will address each separately. Then start the Windows XP installation process. Install the Boot Camp Drivers for Windows, which is included with the If necessary, download the latest Boot Camp drivers that may be newer than the version included on the install disk.
As of this writing, the latest version for Snow Leopard systems is version 3. Leopard systems is 2. Note: There are several other drivers, some for specific systems and others for various Apple peripherals. Make sure the system is running the latest Apple Windows driver components for all hardware and connected peripherals. IMPORTANT: When the Boot Camp Drivers for Windows are installed they install only the components for that particular system including video drivers, bluetooth drivers, ethernet and wireless drivers, keyboard, trackpad and mouse drivers, etc.
When trying to use the same Windows XP, Windows Vista or Windows 7 image on another non-similar system, certain video anomalies, keyboard issues or networking problems may occur. Often, simply installing the Boot Camp Drivers on that new system will resolve the issue. Install all relevant Windows updates from Microsoft. Note: Boot Camp 2. Install any software including licenses. Then click OK. CAB and copy setupcl. When using multiple languages, the i directory must also be copied over. Step through the setup assistant clicking Next after each setting.
Some of your specific settings may vary. Windows 7 Master Image Creation 1. Install Windows 7. Install the Boot Camp Drivers for Windows version 3. Version 3. Simply download the 3. As of this writing version 3. IMPORTANT: When the Boot Camp Drivers for Windows are installed, they install only the components for that particular system including video drivers, bluetooth drivers, ethernet and wireless drivers, keyboard, trackpad and mouse drivers, etc.
When trying to use the same Windows XP, Windows Vista or Windows 7 image on another non-similar system, certain video anomalies, keyboard issues or networking problems can occur.
Install all relevant Windows 7 updates from Microsoft. Install any software and include relevant licenses. The Computers section of DeployStudio offers powerful features for automating the following tasks: 1. Incremental local hostname and computer name information 2. Network settings including: a. DNS servers e. Adding additional user accounts including admin and non-admin users 5.
Start by launching DeployStudio Admin. General - provide the Local hostname and choose the range depending on the number of systems being deployed, then select the Start index at:. Provide a Computer name: if desired. When deploying Boot Camp images, you can add a Windows computer name for Windows and determine what computer group s the Mac client is associated with in Workgroup Manager. Licenses - the Mac OS X Server and Xsan version 1 only License keys are intended for server cluster environments utilizing one or both of these site licenses to deploy to other servers.
Unless you are managing a server farm, most likely you are not using Volume License keys for your servers.
0コメント