Deployment Solution 7.1 SP1 Use Cases
Updated: 19 Oct 2010 | 13 comments
Attached is a use case for Deployment Solution for the ITMS 7.1 Beta product. Please log any issues here in this forum for Deployment Solution. The forum will be monitored by both QA and others to watch for issues that arise.
Discussion Filed Under:
Group Ownership:
Comments
Unable to edit PXE Servers under PXE Server Configuration
I was looking to test PXE and was unable to edit the PXE Servers under PXE Server Configuration. The pencil icon was greyed out.
Looking around Services, I noticed that the following services relating to PXE were set to Manual Startup Type:
After starting all the above services, I was able to edit the PXE Servers under PXE Server Configuration. Not sure if these services need to be set to Automatic Startup Type or if there is another Altiris service that is supposed to start them up like there is on the Deployment Server 6.9.
Services off by default
These services are intentionally set to manual:
"By default, these services are set to Manual run. This is to allow a degree of control over PXE servers and avoid conflicts, and these services need to be started for the PXE boot process to function in the environment." There are more details in this KB article, as well as information on what order to start the services:
DS7.1: How do I set up PXE services on a Deployment 7.1 server?
I assume this is still applicable to the beta release?
The above is currently one of
The above is currently one of my favourite quotes from Symantec as a reason for not implementing something properly. It roughly translates to "Sorry mate -we just ran out of time...."
It's terribly sweet in a way.
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads<
Meant to be fixed....
Someone from Symantec should respond on this one.... I was under the impression that with the release of ITSM 7.1 the updated DS component would have:
For now you can get going to by starting them all up and configuring them to automatic, though you might need to configure dependencies.
There is a split in symantec as to whether you need to set the dependencies as per http://www.symantec.com/business/support/index?page=content&id=TECH127275
Personally, I had problems when I just set the services to automatic. It resulted in malformed proxy dhcp packets being sent from the server when the dependencies weren't configured. The Discovery Control bit which was set to use the boot file name as specified in the packet, but the boot file name (BStrap\x86PC\BStrap.0) wasn't present.
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads<
when I can geit DS 6.9 SP5 beta?
I found there is a license for DS 6.9 SP5,but where I can get it?
Sean
Display Issue When Adding OS Licenses
It looks like there is a display issue when bringing up the dialog to Add OS Licence Key. The text is getting cut off so you can't see the whole field.
Problem after image capture
I ran through the step for capturing an image using an automation folder on a brand new Windows 7 installation. Prepare for Image Capture > Create Image > Reboot to Production. The machine boots to automation and creates the image without a problem, but when Windows boots back to production it stops while "Setup is applying system settings" and displays the following message.
"Windows could not parse or process unattend answer file (C:\Windows\Panther\unattend.xml) for pass [specialize]. A component or non-list setting is specified more than once in the answer file."
This is my first time ever capturing a Windows 7 image and am completely new to the process. I assume that the unattend.xml file in nscap\bin\Win32\X86\Deployment is used for this, but I made no modifications to that file. Should I be, or should this work out of the box?
Jesse Kozikowski
Aspirus, Inc.
Jesse, are you using the
Jesse,
are you using the answer file provided by DS or you are using your own answer file. If you have tried it with your answer file then try with answer files shipped with DS.
~SysPanacea - Remedy for PC problems.
If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.
I didn't supply an answer
I didn't supply an answer file at all, nor was I required to. I'm not deploying an image, where you have the option of choosing the answer file that gets used, I'm creating a new image. The only value I added was the product key to use. So right now Sysprep runs on the computer (the Prepare for Image Capture task) and the computer fails to come back up when it boots back to production and runs through the mini-setup. I'm assuming that the default unattend.xml file is used for that sysprep.
Jesse Kozikowski
Aspirus, Inc.
jesse, can you make sure that
jesse, can you make sure that the product key you have enetered is correct. If you have Vista onward machine, use Current Key option.
~SysPanacea - Remedy for PC problems.
If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.
It's Windows 7 so I changed
It's Windows 7 so I changed it to Current Key, but right now I'm not able to create any Ghost images. The GHOSTERR.TXT file in automation shows error number 662, cannot create image file. I was doing this several days ago, so I don't know why I can't now. Curiously, if I change the image type from "Disk Image" to "Back-Up Image" it'll create the image just fine. I've haven't had the time to dive into the cause yet.
Jesse Kozikowski
Aspirus, Inc.
BTW, Ghost is creating the
BTW, Ghost is creating the necessary directory for the image under "task handler\image" on the test NS, it just can't create the image file.
Jesse Kozikowski
Aspirus, Inc.
Same problem here...
@jessiek: I'm running into the same problem using the default unattend.xml after taking an image of Windows 7 Pro using prepare for image capture and rebooting.
All my license keys are in the system and show up properly. Any help would be appreciated. I've followed a lot of ianatkin's posts and still am having trouble. This is a new installation of DS 7.1 using WinPE and PXE (which are working well).
I'm a bit confused on why after capturing an image the source computer won't come back properly. Any help/advice would be great. Thanks in advance.
Would you like to reply?
Login or Register to post your comment.