Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Deployment Solution
Showing posts in English
Tim.Jing | 07 Feb 2013 | 2 comments

Great call today, Altiris support is like a box of chocolate, unless you are nice to some people and they can get you connected with the right people.

Chatted for a while with Thomas Baird today, he's brilliant like Brent Bishop. 2 of the smartest Altiris guys I've ever had a chance to working with. So on with the items of the day. 

We narrowed our top production issues to 3 main items, with a bunch of sub-issues that I sent to Symantec in an email hoping to have the DS team address with some efficiency. 

 

Issue 1. Machines gets a Device not capable at times. So the issues stems from inventory more than SBS as we originally thought. The NSE processing as Inventory vs Initial Deploy. So Changes were made to initial deploy and testing continues I will say now image to existing machines do work(See issues 3 for more details) but new machines remains to be tested. So the beta solution is fake a InitialDeployment task and get the NSE...

Tim.Jing | 07 Feb 2013 | 0 comments

A lot of questions for Altiris support today. The product is piloting very well to this point with the exception being the Deployment Solutions.

The amount of issues with the product, the oddness of the logic in execution hopefully will be answered by someone in the DS team on a scheduled call today. There is a list of items I'm hoping to get answers for.

1. Hierarchy, why certain things replicate and what for. like Images built for a Child NS server does not replicate up, but the resource guid does. So you can see it at the parent but not assign it as a job.

2. Imaging, lots of issues with the supported method and mechanism that it performs to connect a WinPE machine to a known Guid.

3. PXE or now changed Symantec Boot Services. It behaves badly, and other than restarting services no details or documentations on any possible tweaks.

4. x86 for WinPE has broken Firm files.

5. Replication of PXE configs does not always work.

6....

Tim.Jing | 06 Feb 2013 | 1 comment

Fixed a few things yesterday if you are keeping up with this still. The PXE/WinPE loading issue is working for now. but our cases with Symantec is stacking up.

There are 5 open cases which all seemed to be shuffled around from technician to technicians. When I get time I will be calling the duty manager to escalate them to the DS team as they are almost all DS related.

So the new issues:

Some machines does not always boot in to WinPE. They just wont do it even with a SBS rebuild and only on some jobs. Unfortunately this happened to one of my image machines. It imaged fine on Child Server 1's Site server 1. But will not boot in to PXE on Child server 2's Site server 2.

When an image is captured. Which means we had to force the machine to shutdown after the Syprep. They delete the image capture job and apply a Image capture task. Well now the Image Deploy job will not allow us to populate the Serial # after selecting the image. Look at the red...

Tim.Jing | 05 Feb 2013 | 0 comments

This feels like being smacked at every turn. So Monday morning fresh start, we did get ghost image to work last Friday right?

  1. First up, huge issues, GhostUser account keeps sitting there after imaging. Someone has to go hit the OK button to the GP related Eula for the Ghost job to finish(What ever that task is?) So basically no automation.
  2. Second, 2 of the other Child NS's will not keep pxe running.

Cases put in to Symantec, of course it will be at least a day before we get anyone on the phone. So Google, and Connect it is.

By 3PM, we found the cause of both issues.

1. GhostUser does not log in. There is a new version of DeployAnywhere that resolves this, and it's a known issues since 4-17-2012, why is this not in MP1??? So look and get the files from this link below if you have the same issue.

...

Tim.Jing | 04 Feb 2013 | 4 comments

Finally got Image deploy to work where it would take the computer name in the console!

It starts with Using ghost(Which is crap IMO). Then Using Symantec's built in Capture image job, then deploy. And you have to use 64bit PE because there is a known issue where 32bit PE does not have Firm which causes the unattended.xml to not get copied, and the job would hang and fail after imaging.

So today, more image testing with 32 bit, and throwing out all the great logic we had planned with this product.

 

Original logic:

Image x -> Script in the correct agent installer(hierarchy) -> Copy local all base sw -> Boot to windows and use unattend.xml to install all software and agent.

 

Now it's back to:

Ghost-> Tasks->

 

So the big hurdle. Since Ghost is doing it's thing in the back ground, we have no way to manipulate the agent(It configures to the aprents server the image...

Tim.Jing | 01 Feb 2013 | 2 comments

To put it mildly, the Altiris SMP 7.1 MP1's DS suite is not looking good. And if you have a working DS 6.x, do not migrate to DS 7.x!

Especially if you came from a previous DS 6.x back ground. The pxe now named SBS is flakier than the combo's at Long John Silvers, and the UI design is as simple as solving the Super Strings theory.

So the facts:

PXE works, but it does strange stuff at times and the only way to resume functions when a machine refused to function within PXE is to Stop all SBS services and clear out the Task Handler folder.

PC join domain, naming. Mother of all nightmares. How this could be such a complicated set of dance moves is shocking. This is an Enterprise product?

PC cant be re-named in WinPE, so the randomized name gets used as the PC name after the jobs at times. 

Here is to a good productive day on resolving the PC join domain after imaging issues. But it's future is bleak based on what we are seeing...

Tim.Jing | 30 Jan 2013 | 6 comments

This week, diving deeper in to the functional side of DS with some Windows 7 testing along with software deploying.

So we all know the new DS is different, but I never knew it was going to be this different. And Different is not good at all from an DS Administrator's perspective. So here is a low down.

 

  • Software manager is a mess. Maybe from an accountant's side this may be decent, but for an admin, it bestows more work, more clutter, and a interface that serves hardly any benefits. Bottom line, Too many steps to create a job, and not any benefits over the existing platform.

 

  • New PXE has some issues. The SBS corrupts at times causing machines to give the Device is Not Capable errors. Again, another solution to a problem that didnt exist in DS 6.x or any of the competitor's products. 

 

  • Software delivery is badly executed as well. There are Tasks and...
Tim.Jing | 25 Jan 2013 | 0 comments

The white board sessions seems to get longer, and the endless syntex errors are just a blur dulled by time.

But we are making steady progress. Altiris 7 doesnt suck like everyone said it would, and other than a very crappy(Personal opinion) console design, everything is pretty smooth.

Things accomplished:

Hardware independent image done, took 3 days, completely modular.

Base Software installed through Unattended.xml. Again modular based on what we copy in to the partitioned image duing WinPE.

Agent installer logic build into WinPE with variables to install agent to the correct Parent/Child Server.

PCAnywhere tested and working perfectly.

SQL sort issues kind of resolved- gotta specify ASC and DESC on a few servers. So we just specified for all at the top and let hierchy replicate them down.

The Grocery List for next week:

Populate Software manager for SVS, Desktop Deploymen.

Win...

ohzone - CherylPeterson | 24 Jan 2013 | 1 comment

The Vision 2013 Call for Papers is now open.

Do you have a case study featuring successful implementations of Symantec products? Or best practice tips and trick using Symantec solutions? The Vision team is now accepting proposals for sessions at Vision 2013 Las Vegas.

To apply, simply provide a brief summary of what you would like to cover in the session and why it would appeal to Vision attendees. The Vision team will respond to all applications by February 21, 2013.

UPDATE: The deadline to submit your Papers has been extended until February 21, 2013

You can submit your proposal...

Tim.Jing | 23 Jan 2013 | 0 comments

Alot of subtle changes being made as we move forward. A few products are being piloted and some issues being sorted out.

Pilots:

PC Anywhere is being rolled out today or tomorrow. This will give us a look at how stable the product is compared to Remote Desktop in the DS 6.9 products(Which was a wonderfully reliable product except on multi monitors). Working ok in the lab so far.

Do What?

The Software manager. This is one ridiculous product. it's a library of your installer files(Which means it keep s acopy of everything to do not a whole lot with, wasting disc space?) The software you import in here and add command lines in the package tab can be replicated to the Package servers, but some how this storage space isn't available as a Package server source? Also if we went through the time to import the command lines for the product, how come you still have to go back in and set the newly imported product as Manager? Why would anyone go through the...