Zenworks 7 upgrade

[jrp611]

I am in the process of upgrading my zenworks from 3.2 to 7.0. I would like to be able to install the zdfagent.msi via a login script. I have tried a script of "msiexec.exe /i \\zenserver\public\zfdagent.msi /qn" but was unable to make this run. Any one have a better way to install the program to the computers.

Thanks

 

[Provogeek]

I have placed the script into faq91-6874, after posting, I noticed all of my horrible spelling mistakes as well as a little internal customer information still in the script. So I asked Dave to remove the post for me.

Again, you can find this script in faq91-6874


let me know if you have any questions on how to use it. And please, post those questions here, do not email me with them (because you may not be the only one with questions on how to use this script).

I hope to have a re-write done fairly soon for ZCM agent deployment, but so far, Novell has made the ZCM agent deployment too easy. But I have run into an account recently that seems to have made all the deployment options in ZCM not work, so I may have to fall to this script for it as well.

Keep your eyes on the FAQs

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt SPOOOOON!!!!!
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[jrp611]

Brent,
I upgraded the Zenworks server to version 7.01 the upgrade work out with some minor problems in the apps but they have been fixed. I also used the script that you pointed me to and that worked real well. The only thing that is strange is that when I go in to the Users policies to make changes to the windows policies. Then try to exit out the policies the screen stays on that screen for quite a while after it close out then I can apply the settings and exit out of consoleone. Do you know if there is something in consoleone that can be tweek to allow it to exit out a little bit faster.

 

[Provogeek]

Nope, thats normal behavior.

This is what is happening.

You click that snazzy edit button to edit your policy,

Your default local policy is backed up and placed into a temp location on your local disk.

The MMC opens up and allows you to edit your policy.

** Notice that any changes you make take affect on your system as you do it (at least most, there are some that require a reboot to take affect). This is because you are editing your local policy files. **

You create a total lock down policy to prevent your users from messing them selves up by accidentally deleting their own network connection (yes, I have dealt with a user that did that ... don't ask, he was a lawyer).

You close MMC,

the local policy files that got edited get copied up to the network location you specified in the Zenworks Policy settings. Then your default policy that got backed up is restored.

Not the fastest thing in the world.



Note: I always recommend to my customers to either go out and buy VMWare Workstation or use a spare workstation to manage the Group Policies that will be deployed by Zenworks. I have been bitten to many times (twice) by using my production PC to edit a group policy, and the restore process failed. Really messes up an evening having to hack your own system to remove a group policy built to be used on a kiosk system.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt SPOOOOON!!!!!
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com