Deployment and Imaging Group

 View Only

Ghost Solution Suite 3.0 Imaging FAQ page 

Jul 13, 2015 01:16 PM

Please find below the most frequently asked GSS 3.0 imaging questions:
 
Q: Are there any unique advantages to using RDeploy instead of the Ghost imaging client?
A: RDeploy is included in GSS 3.0 for legacy purposes only, it is deprecated and will be removed in the next version.
 
Q: What about rdeploy? Will it still be used or is it gone with GSS 3?
A: RDeploy is included in GSS 3.0 for legacy purposes only. It is deprecated and will be removed in the next version.
 
Q: Will Ghost 3.0 boot allow USB image creation and reading of image files without the need of access to the Ghostcast Server?
A: This can be achieved through customization. 
 
Q: Can I ghost a MAC OS? I assume Ghost Explorer is not compatible with a MAC OS but I would like a simple overview as to what specifically can be done?
A: Native Mac support in GSS 3.0 is management only. But, Mac imaging can be done using guides such as:
http://www.symantec.com/business/support/index?page=content&id=HOWTO8571&actp=search&viewlocale=enUS&searchid=1290008888117
http://www.symantec.com/connect/downloads/mac-imaging-using-deployment-solution-unicast-multicast
DS 7 includes native Mac imaging. 
 
Q: Will the newest ghost binaries work with ghostcast from version 2.5? 
A: We don’t test this combination but it is highly likely to work.
 
Q: You also mentioned that we can pre-defined the computer list for imaging. Is there a way you can named the workstation as you start the job, creating the workstation name after you start the imaging/deployment job?
A: When you create a computer in the console you can name it whatever the final name should be. Then we have the concept of tokens which can be used in the Sysprep process where the tokens are automatically replaced at run time. This means that you can create a single job and run it on any machine and it will pick up the new name from the machine record. The capabilities in GSS 3.0 to customize the imaging process are far advanced compared to GSS 2.5, I hope much of this new functionality will prove useful.
 
Q: Are there any significant performance enhancements to Ghost32/64.exe Ghostcast.exe? 
A: Not in this release. We do have some updates planned for imaging speed in the coming releases.
 
Q: Will GSS 3.0 Support a stand alone imaging process so a user can create and/or retrieve a image file independent of access to a Ghost Console ?
A: GSS 3.0 includes the Ghost standard tools which is a full suite of tools to create a customized imaging process. This is entirely independent of the Ghost console.
 
Q: Does 3.0 Support a similar image we use in 2.5
A: Yes, the core imaging technology is identical so you will have backwards compatibility.
 
Q: Where is the speed increase with GSS 3? Maximum deployment for me is still ~1800MB/min unicast with great hardware. I can deploy a Mac using DeployStudio ~ 3600MB/min with equitable hardware server and client, same network config    
A: The short answer here is that we haven’t improved speed in this area. We will improve imaging speed but it’s a little further down the line. We have a lot of work to do regarding usability and modernization but will be working on this in parallel.     
 
Q: If I remember right, there used to be a utility to convert a boot disk image into an executable that could be run the desktop on the system being imaged.  Is this still an available function in the new product?    
A: We’re looking at returning this to the product, updates will be available soon.
 
Q: Are we able to push gss 2.5 sysprepd images using GSS 3.0 with the "prepare using sysprep" check to apply updates to this image?    
A: GSS 3.0 is backwards compatible with images GSS 2.5.
 
Q: Was the ghost deployment process utilizing UEFI boot or legacy?
A: We support both.
 
Q: ­So to easily use Multicast, I need to create my boot disk using the GST Boot Disk Creator?­
A: ­ Yes the GST boot disk creator will make a standard boot disk that can be used to join your ghost cast sessions manually by booting from a disk as you may have done so in 2.5 if you were not using the Ghost console/client. 
 
Q: Where would the -ntexact switch be entered?    
A: Into the command line as part of the image deployment job.

Q: Can you map a share for images only?
A: You can map as many drives as you need during the final stage of creating a boot image. Just add them to the final stage where you get to edit the ini file.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.