This Question is Answered

1 "helpful" answer available (10 pts)
2 Replies Last post: Jul 1, 2009 1:04 PM by SPCSecurity  
SPCSecurity Rookie 2 posts since
Jul 1, 2009
Currently Being Moderated

Jul 1, 2009 12:30 PM

Replacing client files for Software Deployment Portal?

We are starting to add programs for the Software Deployment Portal (v. 8.8 SP2) for our users.  Many of them already have the updated agent; we still have a few stragglers who aren't reporting in.  In order to allow the end users to install certain non-licensed software and ease the load on our help desk, we want them to use the portal.  To that end, I've customized the HTML and CSS files.  My question is this: what is the best method to push the three files (policy.portal.template.htm, policy.css, and our company logo) to our end users?  If I replace those files in \\server\\ldlogon\policyweb and push out the agent again, would their local files be updated?  Is my line of thinking correct?  If not, what would be a good way to update their files so they see the customized Software Deployment Portal?

Gerald SupportEmployee 47 posts since
Mar 7, 2008
Currently Being Moderated
1. Jul 1, 2009 12:58 PM in response to: SPCSecurity
Re: Replacing client files for Software Deployment Portal?

You are correct about if you update the files in ..\managementsuite\ldlogon\policyweb on the core that all subsequent agent installs (or reinstalls) will get the updated files. So you can reinstall the agent and the files would get updated, or I guess you could create a little script that replaces those files on the client with the ones on the core if you don't want to push down a new client.

More Like This

  • Retrieving data ...
LANDesk Community powered by Jive Software's Clearspace ® Subscribe| Legal Notices| Investor Relations| Avocent| Privacy Policy © 2009 LANDesk Software