Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Client Management Suite
Showing posts in English
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...

ArthurV | 30 Jan 2013 | 0 comments

I had an issue where I would run a Task like 'Update Client Configuration', but the NS would show a ‘Failed’ status after a few hours.  On the client, it would show 'Success - return code 0'.  The reason it failed was because the 'Altiris Client Task Data Loader' service was not running.  I tried starting the service, but got a ‘Error 1053: The service did not respond to the start or control request in a timely fashion’. 

The solution for me was to follow the instructions provided by K. Kennedy at https://www-secure.symantec.com/connect/forums/altiris-client-task-data-loader-service-wont-start.

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...
Ludovic Ferre | 29 Jan 2013 | 0 comments

Update! Added the Dataclass and Filters top level items as they also needed fixing. Also I added a reference to my original SP1 to SP2 upgrade post, with steps for fixing the issue [1].

####

I attended an upgrade for a customer installing MP1.1 on 4 servers in hierarchy (1 parent, 3 children). We had some minor problems when we got started but nothing major:

  • 2 servers (including the parent) did not have the MP1.1 upgrade option because SMP 7.1 SP2 was not appearing as installed in SIM. We just ran the upgrade as a new installation.
  • The parent configuration went much to fast to be healthy. In effect it did not install most of the products, so we ran the "aexconfig /configureall" manually and this fixed the environment
  • One role had been granted undesired rights (inherited from the hidden parent folder)  on main console locations: "Reports", "Console menu", "Settings"...
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...

Ludovic Ferre | 23 Jan 2013 | 0 comments

The Symantec product listing xml was updated Monday.

Here are the information we have from it:

File name: symantec_v2.pl.xml
File hash: 3e447dd07844f9fad531a3240215a11b
File date: 2013-01-18 15:37
File size: 13,990,445 bytes (~14MB)
Release date: 2013-01-21

From the Git commit [1] we can see the following changes:

 

  Add /solutions/7_1/mobilemgmt/7_2_sp2_1_rtm/symantec_mobileframework_7_2_sp2_1_x64.msi_info ...