Tool

Submitted by geoffc on 4 June 2009 - 5:06am.

I have not tried it yet, but reading through the docs, looks very nice!

Well done! Thanks for contributing such a useful tool!

Submitted by shanedriggs on 8 June 2009 - 12:58pm.

We are about to do this and this is going to make life some much better.

Submitted by frichi on 26 July 2009 - 7:09pm.

We trying to run this utility, but we receive the error "Line -1 Error: Variable used without being declared"

Submitted by egarcia on 3 August 2009 - 1:03pm.

It doesn't seem to autologin after removing the ZfD agent. How do you set the autologin feature?

Submitted by Provogeek on 3 August 2009 - 2:55pm.

The tool has been updated today, you can download it at http://www.novell.com/communities/files/ZCMScriptW...

The problem folks were encountering was due to an issue in the base script. A customer request had me add the auto login function earlier than I had planned. So as to not mess up my code base, I used a customized branch for this customer. Well, not being a full time programmer and not having much of a method for tracking code changes, I goofed up when I merged the new functions into the script. There were changes in the names of variables, and I did not update those changes properly in the public code. So I have been spending the past week sifting through the code and making sure all the variable names match up and have been running various tests to ensure I post a working script this time.

Submitted by Provogeek on 13 August 2009 - 11:10am.

Sounds like you downloaded a previous version, to get around this error you will need to delete the directory I use for script building. The directory is located in %USERPROFILE%\Application Data\ and is named ZScptWiz . Delete this whole directory and try building a script again.

The reason this is happening, is that the EULA portion of the script only runs if it does not find the EULA text files, doesn't look for any other file. If it finds the EULA text files, then it skips the EULA pop up windows and proceeds to the script, since it is assumed you have seen and read the EULAs already. If the script does not find the EULA text files, it will then present you with the AutoIT EULA and the KIS EULA. Once accepted, the AutoIT and the needed support files are extracted from the distribution executable. This is the only place the support files are extracted. So if you have already seen and accepted the EULA, the files are not being extracted.

I made a minor change in the current version, and that was adding and icon graphic to the compiled script. Wanted to have something other than the default AutoIT icon. That icon file was not in the previous version. So since a previous version was run on your PC, and the script finds the EULA text files, the ico file being used when compiling is not being extracted.

Thank you for the heads up on this, didn't think about this problem in my testing. I'll code in additional checks to ensure needed files are in place and are correct version in the next rev of the tool.

Submitted by Lesnikovr on 19 August 2009 - 3:05am.

When I executed a script I received an error "Unable to remove ZENworks application ZENworks Remote Management" in a log file.
After that uninstallation of the agent was aborted. What can I do to correct this?

When I tried to install the agent using this script on a computer with no agent - the scirpt was not executed. I don't understand why. Please help. The computers are in a domain, the user is an admin on that macine.

Submitted by Lesnikovr on 19 August 2009 - 3:07pm.

Please, continue work with improving removal process for 10.1 and 10.2 agents!

When the script aborted in my situation no errors was written to log file. Now I made the script to work and today have some wishes.

I would like the script to save configuration settings for future use it.

My situation is the following. I deployed the agents to workstations and then embedded database crashed. I had to re-install sever to another platform with external database and the problem was how to re-assign the workstations to a new server remotely. I wanted to unregister, update ceritificates and then register the workstations but using NDS login script without admin rights failed. Now I'm testing your solution and I hope it will help me to solve the problem/

And the last question: If the agent already exists on the machine and assigned to the new server does the script remove and re-install it? How can I make it to uninstall only ZCM Agent on those workstations which assigned to old sever with wrong certificate and IP-address?

Thank you for your answers

Submitted by Provogeek on 9 September 2009 - 4:31pm.

I had some time today to address the uninstall function of my script. Since none of the MSI uninstalls remove the pre-agent, I simply remove the service after uninstall (similar to the BAT file found in the Novell forums). So the uninstall works now as expected. An update to the script has been tested to verify the uninstall/reinstall function works.

I do need to note however, that the intention of the uninstall/reinstall routine were built for two reasons. First being the undesirable event of removing ZCM from a network with out the intention of putting it back. The second being an agent that was not install properly or had a failed install that a normal add/remove could not correct.

The script should not be used for the purpose of changing a workstation's zone (even thought it technically can be used this way). The process of adding a workstation to a new zone in the event of a zones primary CA server crashing should be done using the zac tools that come with the agent. TID 7000620 has excellent instructions on how to move a workstation to a new zone. The reason I suggest people use the method in the TID is that it takes 10 seconds, no reboot on the workstation, no interruption of the user (must be done in login script). Using my deployment script to accomplish this will take 15 - 30min and require a reboot.

Submitted by chrisflure on 11 June 2010 - 5:51pm.

Provogeek,

Ok, on my last comment disregard, I can now see how to edit the script. Do you know what line I need to change?

Thanks!

Chris

Submitted by metheridge on 25 September 2010 - 1:42am.

Thanks Provogeek. This latest update is much appreciated.

Submitted by tjacksonbcg on 21 November 2011 - 1:08pm.

Any idea why I would be getting the Windows Run As prompt when launching the compiled executable on XP SP3 as a user? I specified correct non-domain admin credentials in the script builder.