Video Screencast Help
Endpoint Management Community Blog

DS7.1sp1 : Some (silly) facts for the product team

Created: 11 Sep 2011 • Updated: 12 Sep 2011 • 1 comment
Bourdin Laurent's picture
+5 5 Votes
Login to vote

I wrote this words to answering in another bog entry, but I think these simple facts are so significant that they can be a stand alone blog entry if some product manager or devellopper read this blog.

Just for fun, some DS7.1 integration way :

- You have a wonderful tool to create PXE Preboot (Bootwiz). This tool include an agent (Dagent for DS6.9) and a way to include OEM (Dell, HP,...) tools. When you want to change the Agent (PECTAgent for DS7.1), the Symantec way is to drop the original agent and add the new agent through the OEM function. It's ... dirty ???

-You have a tool to replace tokens in your Tasks scripts. You want to implement a replacement token tool for unattend and sysprep files. Extanding the usage of Tokens is not a good idea, it's better to creat a new token replacement process without any user control (changing the %TOKEN% to @TOKEN) and put this tool directly on a dll on the PECTAgent. It's ... stupid

-You deploy a new Agent (PECTAgent) without any Inventory ability. It's shure, no one need to now the computer product name when you deploy a computer. It's ... idiot ???

-You deploy a new OS with the wonderful SOI tool on DS7.1. The SMP and deployment agent installation is made through the SetupComplete.cmd method. OK. So you copy the entire sources from the task server ? NO, it's too simple. You prefer deploying the Bootstrap tool and download the sources directly from the SMP server (23Mb accross a WAN...). I prefer no to talk about the DSPluginIstall.exe ans his Registry Tweaks, it's just ... funny ???

-Last but not least : Bare metal Deployment. Deploying software directly after deploying an operating system is too simple. You have to create a server job; deploying a software is not possible on a computer without the Software Management Agent. The only thing that the Software management agent have to do is : Talking to the SMP server that the computer use a license. Create a tool to populate the license table at the begining of the job would be too easy for customers; It's ... bull****

DS7.1sp1 just work. For me it's not a real product today, just some bricks putting by some devellopers without any management. But it works. You can deploy Operating Systems through a web console. But if this product still live in 2014, I hope that every point I've wrote will be replaced by real products.

Just for your knowledge : I've deployed more than 5 client on DS7.1SP1 (and more than Thousand clients on DS6.9 and NS6.x/7.x) and it's not over. I expect a lot of change for the SP2 (or 7.2....)

Please Symantec, add some quality....(The last one : DS7.1SP1a doesn't include Task Serve Handler -aka PXE Tools- for x86 servers, see  http://www.symantec.com/docs/TECH167515 ...)

Regards
Laurent

Comments 1 CommentJump to latest comment

Pascal KOTTE's picture

You are right, We need to patch the doslution with a lot of "best practices" to making the product ready to use.

Like, creating a sscript to inject the Soft manage plugins before during OSD.

going to import from a KB for finishing the propuct install: (see http://www.symantec.com/docs/HOWTO44396 for those msissing it :)

It looks like a Microsoft solution, before, during the time where only developpers were able to make a

Times are changing, Microsoft is more and more -pre-integrated ready.

When looking on Ds 6.9: the tools is there, ready to use quickly.

When looking on DS 7.1: we feel a regression, because a lot of things to "manual" correct, and learn, to make it usable.

I do not deliver here "my own" point of view, but all the feedbacks from customers making the "evaluation"  DS 7.1 are converging:

"DS 6.9, we were able to make it works easily, with 7.1, we don't understand what to do to make it works..."

~Pascal @ Kotte.net~ Do you speak French? Et utilisez Altiris: venez nous rejoindre sur le GUASF

0
Login to vote