Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with 7.x
Showing posts in English
Tim.Jing | 18 Feb 2013 | 3 comments

To create a good product it requires lots of talent, great team work, and really good communication. To have a great product, the entire team needs to be focused and driven.

Up to this point, Symantec has some of the best sales people, a good Sales Engineering group, decent technical support team, but where is the communication with the Dev group? How come we never hear from those guys? Are they locked away and not getting the feedback from the users?

This will be our 7th week with the Symantec SMP 7.1 MP1 product, and while 90%+ of the suite is working or workable, we continue to have imaging issues. While i'm optimistic that Symantec has the resources to resolve our issues, it's rather unfortunate that the basic functions do not work out of the box. At least not reliably, which their 6.x version did without any issues. 

So moving on to next week, focusing on the same imaging issue, but with more detailed problems:

1. Deploy Anywhere will...

Tim.Jing | 15 Feb 2013 | 0 comments

With a lot of help from Symantec, we narrowed down some of the issues with image deploy. And it's all timing related, which is another word to say product design?

When a machine that has any changes other than whats already reflected in the database (New machine, existing machine's F8'ed in to a task server, a machine that just had a name change...) The database needs a resource membership update, and this machine is not allowed access by any of the software tasks due to licensing/client not capable.

So lots of Delta Reource Updates for most o the error messages. And more calls to come with Symantec Support.

Check out the screen shot below. This actually means, some jobs ran, but at least 1 failed. And you have to click on everyone to find which one failed.

 

:)

 

Tim.Jing | 11 Feb 2013 | 0 comments

It feels like my freshman years in the IT business, where there is no fear, not a single worry. Beer and pizza will be there later, and all things will work it's self out.

Well I am lost for words on this product deployment so far. Lots of bells and whistles to see in the Altiris 7.5 SMP, tons of automated actions that you don't have to script to do. Something you can train even beginner IT forayers to use in the console when it comes to software management, Patch and Inventory.

Until you get to the DS, we suddenly have lost our ability to image machines. As in issues on both Notification servers, separate issues, different errors. But bottom line is simply we cant reliably deploy any images.

The issues seems to relate to either timing, or design. The NSE's are supposed to get processed with priorities, and since inventory is one of the least important it becomes at the back of the line. So we went to Initial Deploy as a method for sending a highly...

Tim.Jing | 08 Feb 2013 | 1 comment

Sorted a lot of items today, most discovery and not fixes.

Discovery of a lot more issues that is. All DS and imaging related. Here are some of the crazy scenarios.

1. Build a machine with the predefined spread sheet, and the machine did not join the domain. After a manual joining to the domain, the machine enters WinPE every time. In the console there is now 2 instances of it, one with IP and domain info. The other which is just blank.

2. Any machines that needs an image job on our second NS, Jobs gets the error of either "Not Capable", or "Unexpected error while saving this schedule"

3. Image is a crap shoot at this point, there is no telling which service, directory, files to clean up. Like voodoo.

But found 1 cool trick out, you can resize the pesky window sizes if you grab it at the top of the sizing bar(Red dot).

And interesting PXE bounce when the PXE configuration fails to replicate settings from the parent....

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...