Video Screencast Help

Imaging with Deployment Solution 7.1

Created: 25 Jan 2012 | 10 comments
NeilSmith's picture
13 Agree
0 Disagree
+13 13 Votes
Login to vote

I think it would be advantageous for many Altiris administrators who deal with HII to be able to call upon the Initial Deployment Menu for known and unknown machines.

In the Initial Deployment Settings menu can you create a toggle switch (or radio button) with two options:

  1. Load the Initial Deployment Menu for only Unknown Machines (default)
  2. Load the Initial Deployment Menu for all machines.

Comments 10 CommentsJump to latest comment

Sally5432's picture

I didn't see this before and just submitted same idea.  This would save our technicians from dealing with the console at all at imaging time and be a great improvement in the product.

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

0
Login to vote
NeilSmith's picture

I hacked and slashed and was able to get the Initial Deployment Menu to load on all machines. It is VERY messy but my client insisted upon using the menu. Anywho if you are interested I can show you how to get that done.

0
Login to vote
MJammer's picture

I want to try using initial deployment menu in our environment and see if it suited for us. I did get the menu working a couple weeks ago all of a suddon. Recently I needed to build a brand new PXE Configuration, now initial deployment menu does not appear anymore.

PC boots to PXE > WINPE loads > Automation wallpaper appears > cmd prompt opens and runs it's .dll files and lastly "Calling custom actions..." then minimizes. Now the pc just sits at the empty automation wallpaper screen. It used to bring up initial deployment menu with a image deploy job and a reboot task(default) withing 20 seconds. Now it doesn't anymore since I made a new pxe config. My old configs are removed. So I cannot go back to antyhning made in the past.

0
Login to vote
Rubensann's picture

I am interested as well,

I will be deploying many site servers with DS component, most of them will use PXE (as requested by the client) to boot new PCs without OS installed.

 

Regards,

Ruben

0
Login to vote
Thomas Baird's picture

That is, essentially the same screen, but will show up on any managed system booted to WinPE without a job assigned already.

This will be available in the 7.5 Orion release of DS (shipping with ITMS)

For those of you waiting for 7.2, it was moved to 7.5 to better synchronize with the rest of the products, and adding more MAC support, among other things.  Yes, it's a delay, but it'll be better for the product.  I promise!

Thomas Baird
Looking for opportunities
(translation: unemployed!  LOL)
Yes, able to help people beyond the forum if need be.

 

0
Login to vote
Sally5432's picture

when is 7.5 scheduled for?

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

0
Login to vote
Ray OConnor's picture

Yes, when it that schedule to come?

0
Login to vote
JMRoberts's picture

Any news on a release date or a quick fix?

0
Login to vote
Sally5432's picture

7.5 date has been pushed back with nothing set in stone.  They found bugs in testing.  I run CMS 7.1 and installed MP1 and have more issues than I had previously - install with caution if you haven't already.

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

0
Login to vote
MJammer's picture

I also hope this will be available in version 7.5. I ahve tried using imaging jobs through PXE with initial deployment menu but I can only get it working with unknown workstations. Once the Symantec Console manages the workstation and that computer needs to be re-imaged for any reason, initial deployment menu will not appear after WIN PE loads.

 

Right now I use a customized boot cd that maps to our HQ altiris 7.1 server. The helpdesk tech browses to the correct folder > image file made with RDeploy. Itinital Deployment menu would be great to eliminate the browsing to the right image. Right now I have five images for Windows XP and three images for Windows 7 x64. All of them in a folder labeled for the situation. It would be nice to make up the menu and label the image. I came off of using Novell ZenWorks 7 where the Novell Consultant made a wonderfully customized boot cd that knows the ip segment you are on and pulls from the correct imaging server (there were a few Zen Servers with our LAN) and a numbered text menu with the numbers pointing to the image file you need. ZenWorks Config Mgr purchases did not go through for us so we moved off of Zen and onto Altiris 7.1. A learning curve involved, but I am making strides in the imaging area, and slowly making my way through the application packaging/policies.

 

When initial deployment works with unknown/known workstations I want to build a thin image and have application packages get installed through the imaging job. Windows 7 images are up to 7 GB for myself.

0
Login to vote