To enable capture of these events, we must first disable the " Enable Verbose Reporting of Package Status Events " option on all existing packages on the Notification Server. To do that, the following SQL statements are given as a hint:. Important Step 1 There is a slight possibility that the state column may be greater than 8, for packages. Step 2 If the values returned by the above query are below , proceed with this query:.
The Altiris Agent deployment settings are configured to roll out the Agent with an admin account, rather than the Application Identity credentials. The NS. Weekly Scheduled Task and other scheduled tasks are configured to run with the Domain Admin Credentials. The cloned Default Software Update Plug-in Policy targeting the affected client was generated from another cloned policy. Work through the following to resolve each issue: Contact your Sales Representative: opt.
Ensure the upgrade is enabled. Set these to run ASAP and on a repeating schedule to ensure the clients are able to get the plug-in.
Check communications and ensure downloading is allowed for the client. Migration User Apr 21, PM. Skip to main content Press Enter. Sign in. Skip auxiliary navigation Press Enter. Skip main navigation Press Enter.
Toggle navigation. Search Options. Client Management Suite. Back to Library. Apr 19, PM. Migration User. Disabling this policy allows service accounts in the background to deploy the software without requiring consent to a dialog for installation.
We use an AD Altiris Service Account that does the heavy lifting of installing programs in the background. This will allow it to not encounter problems with the actual installation of software. The second component to all of this is verifying that the communication between the Altiris Agent and the Notification Server is stable and consistent.
What I would find is that for some reason after pushing a package out for installation, the first would be successful but every subsequent install would fail. I looked at the Event Viewer Security logs and would see reference to the Filtering Platform policies changing with regard to Teredo. Teredo is an IPv6 technology and this made me remember that there were some DAgent issues with it in the past.
I turned off IPv6 and started to push out packages again and I was able to successfully and consistently push out packages to my Windows 7 client.
The final takeaway from this is that as of now, setting the UAC policies as stated above and turning off IPv6 on the clients enabled consistent and reliable Software Delivery with NS 6. I have talked to Symantec at the Vision Conference and in terms of 7.
0コメント