Client Management Suite

Hi

Has someone find a way to automate installation of site services on the site server? Simply installing the needed subagent is not working. After that I still need to "activate" the site service in the web gui.

Regards
Stephan

Hi,

The situation with site-services install is different for different services.

Package Server: if you install it manually from NScap and then run on NS scheduled task "NS.Package Server Status Event Capture Item" then Site Server definition will be added for corresponding computer to Site Server page. This should work for any versions (at least from 7.1 for sure).

Task Server: similar functionality has been added starting from 7.5.SP1 - you may manually install TS from NSCap (just ensure you will select proper msi for install: x86 for x86 platform and x64 for x64) and then execute windows schedule task "NS.Restore Task Servers". New Site Server with Task Server service should be added.

For monitor and for deployment services such functionality does not exist (at least per my knowledge).

Thank you,

Alex.

Hi

I've tried the procedure you've written with the package server setup. But for me it's currently not working. Package Server has gotten a list with packages that he should download. But he's unable to download them and on the NS (7.5 SP1) I got many errors like that:

GetPackageInfo.aspx was called by non-package server with Package Server request type -  resource: 111d3932-ce4b-4b7a-bf2c-8dbe3c7dcbb1. The response will not be generated
-----------------------------------------------------------------------------------------------------
Date: 7/30/2014 7:17:21 PM, Tick Count: 801843 (00:13:21.8430000), Host Name: SRV0003, Size: 450 B
Process: w3wp (3840), Thread ID: 5, Module: w3wp.exe
Priority: 2, Source: Altiris.NS.StandardItems.SiteServer.PackageServer.PackageInfoProvider.ValidateRequestParams
File: C:\ProgramData\Symantec\SMP\Logs\a.log

and

GetPackageInfo.HandleRequest
The agent is not a package server.
   [Altiris.NS.Exceptions.NSComException @ Altiris.NS.StandardItems]
   at Altiris.NS.StandardItems.SiteServer.PackageServer.PackageInfoProvider.GetPackageInfoImpl(CodeProfiler cp, String requestXml, Boolean alreadyRedirected, Boolean internetRequest, Boolean& responseRedirect, Boolean& foundCodebases, Guid& resource)
   at Altiris.NS.StandardItems.SiteServer.PackageServer.PackageInfoProvider.GetPackageInfo(String requestXml, Boolean alreadyRedirected, Boolean internetRequest, Boolean& responseRedirect, Boolean& foundCodebases, Guid& agentGuid)
   at Altiris.Web.NS.Agent.GetPackageInfo.ProcessRequest(Byte[]& packageInfoData, String& packageInfoXml, Boolean& compress, Boolean& responseRedirect, Boolean& bEncrypted)
   at Altiris.Web.NS.Agent.GetPackageInfo.HandleRequest()

COM Exception errcode: 0x8005600B

Exception logged from: 
   at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception, String footer)
   at Altiris.NS.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
   at Altiris.Web.NS.Agent.GetPackageInfo.HandleRequest()
   at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
   at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.HttpContext.InvokeCancellableCallback(WaitCallback callback, Object state)
   at System.Web.UI.Page.AsyncPageBeginProcessRequest(HttpContext context, AsyncCallback callback, Object extraData)
   at ASP.getpackageinfo_aspx.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object data)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
   at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
   at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
   at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
   at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

**CEDUrlStart** :http://entced.symantec.com/entt?product=SMP&version=7.5.3153.0&language=en&module=Dnf2wsKxg8Cghmjlvs6qe5Mw/ttx+N0ZL3/64zAh6ZFw9svGjWrxdJsffMVK3S+J&error=-1937372969&build=**CEDUrlEnd**
-----------------------------------------------------------------------------------------------------
Date: 7/30/2014 7:17:21 PM, Tick Count: 801843 (00:13:21.8430000), Host Name: SRV0003, Size: 3.59 KB
Process: w3wp (3840), Thread ID: 5, Module: w3wp.exe
Priority: 1, Source: Altiris.Web.NS.Agent.GetPackageInfo.HandleRequest
File: C:\ProgramData\Symantec\SMP\Logs\a.log

I confirm that Alex is right about how to automatically add managed servers as Task Server or Package Server, after SMA and TS/PS installation via packages from \NSCap\ folder on servers and then just execute a required scheduled tasks on NS servers.

It works correctly for 7.5 SP1 release, when versions of SMA and Site Server plug-ins are up-to-date to 7.5 SP1 version on remote Site Servers, which weren't manually added by admin as Site Servers on Site Server Management page within SMP Console.

• Make sure that this Package Server and SMA has latest version of 7.5 SP1 release
• Server with Package Server is registered (Check "Agent Registration Status" report)
• "Legacy Agent Communication" policy is enabled, in case if this remote Site Server is lower than 7.5 version.
• Check whether this PS Server exists in "Blacklisted Host Computers' filter or not.

Thanks,

IP.

Also you can find useful informaiton in case if managed enpodint was blacklisted

• https://www-secure.symantec.com/connect/forums/blacklisted-pcs-how-resolve

Hmm, this is not something expected.. May you check SMA agent computer that is going to be the site-server - does "Package Server" tab shown in agent UI? If not, then I suppose PS install was not succeeded because some pre-requisite is missing (maybe IIS role is not enabled?). If this is the case, then please try to add IIS and then launch PS setups again. If IIS present and PS still non-functional then, if possible, please share logs from NS and PS and PS computer OS details.

Thank you,

Alex.

After resetup my test environment from scratch it's now working. Don't know what was wrong before. 

The answer for PS is:

One MUST install/uninstall PS service via NS Console UI.    

UI of course is a front end of the C# API 

Installation of the PS from the SMA side requires running the Windows Schedule at NS:

NS.Package Server Status Event Capture Item.{f85fe5d9-005a-40ac-b213-944b496405fe}

to force  a machine with PS agent to become an "acknoledged" PS.

This schedule runs at 3.05 AM by default.

If some C# scripting at NS is acceptable I may provide that as well if required