DS 7.1 WINPE automation "Capture Image" fails
We just recently had Altiris Endpoint management installed in our environment. We're using 7.1 and are having difficulty getting the automated imaging piece to work correctly.
As it stands right now we were able to mangle our own scripted capture/download image jobs by making custom script tasks and mapping some network drives that upload or download the image. The problem with this is that there is no GUID folder and the image resource does not show in the console.
When we try to use the built-in "Capture Image" job I get the following error message in multiple log files.
We have a number of "CryptDecrypt failed" messages along with a "command to get n/w credentials failed" entry in the Agent.Log and PECTAgent.log files.
We are simply trying to use the automation partition and not PXE at the moment.
Any guidance in this manner would be great.
Comentarios Comentarios • Ir al último comentario
Try Copy File task in WinPE Preboot with some file or folder copy and let us know if this task is also having the issue of "command to get n/w credentials failed" becasue this also do something similar to Create Image. Thanks.
I'm actually able to execute a script that launches ghost and an image capture while it's in automation. The problem is with the built-in "Create Image" task throwing up these errors...
Under the \\LocalHost\Deployment\Task Handler make sure you have the IIS_USRS and NTFS IUSR applied to this directory and then try the job again and see if the n/w cradentials goes away.
I see IIS_IUSRS on the box and added it to the deployment share, but I don't see NTFS_IUSRS
K, Try with that user added and see if you get by that error.
same error in the ClientCaptureImage.log file
"Command to get N/W Credentials failed"
Logs sent as requested Nathan
Case opened
Although case is opened by you but please confirm if you can do "Copy File task" in WinPE Preboot with some file or folder copy and not script execution which could work as its part of NS whereas Create Image or Copy File are DS codes :)
I made a job that boots to automation and then tries to copy a text file to C: and the ClientCopyFile.log file shows the exact same error as other deployment tasks.
"Command to get N/W Credentials failed"
The same file copy job also fails when run in production
This is what appears in the server Altiris log viewer when the "Command to get N/W credentials failed" occurs on DS job.
SecurityCache.CurrentIdentityMembership accessed without security context data set. Location: at Altiris.NS.Security.SecurityCache.get_CurrentIdentityMembership()
at Altiris.NS.Security.SecurityCache.Demand(Guid entityGuid, Guid requiredPermission)
at Altiris.NS.ItemManagement.Item.CheckPermission(Guid Permission)
at Altiris.NS.ItemManagement.Item.CheckCanGetItem(IItem item, IEnumerable`1 accessPermissions, ItemLoadFlags itemLoadFlags)
at Altiris.NS.ItemManagement.Item.GetItemInternal(Guid itemGuid, IEnumerable`1 accessPermissions, ItemLoadFlags itemLoadFlags)
at Altiris.NS.ItemManagement.Item.GetItem[T](Guid itemGuid, IEnumerable`1 accessPermissions, ItemLoadFlags itemLoadFlags)
at Altiris.NS.ItemManagement.Item.GetItem[T](Guid itemGuid)
at Altiris.Deployment.PreImage.get_ClientAgentHandlerXml()
at Altiris.TaskManagement.ClientTask.Data.AltirisSQLDataEngine.GetTaskItemData(TaskVersionGuid taskVersionGuid)
at Altiris.ClientTask.Server.ClientTaskCache.GetTaskItem(TaskVersionGuid versionGuid)
at Altiris.ClientTask.Server.Jobs.ClientJobExecTaskBase.BuildExecuteTask(IClientTaskServer server, TaskInstanceGuid parentTaskInstanceGuid, AltirisResourceGuid resourceGuid, JobInputParameterMap inputParamMap, ClientJobState jobState, IClientJobExecNode baseNode)
at Altiris.ClientTask.Server.Jobs.ClientJobExecTaskBase.Execute(ClientJobState jobState, AltirisResourceGuid resourceGuid, IClientTaskServer taskServer, IClientJobExecNode baseNode)
at Altiris.ClientTask.Server.Jobs.ClientJobExecTaskNode.Execute(ClientJobState jobState, AltirisResourceGuid resourceGuid, IClientTaskServer taskServer)
at Altiris.ClientTask.Server.Jobs.ClientJobHandler.ExecuteScriptNode(IClientJobExecNode node, ParameterValueCollection inputParameters)
at Altiris.ClientTask.Server.Jobs.ClientJobHandler.ProcessNextScriptNode()
at Altiris.ClientTask.Server.Jobs.ClientJobHandler.ExecuteOnRemoteResource()
at Altiris.ClientTask.Server.Tasks.BaseRemoteClientTaskHandler.OnExecute(AltirisResourceGuid assignedResource, ParameterValueCollection inputParameters)
at Altiris.ClientTask.Server.Tasks.BaseClientTaskHandler.Execute(ITaskExecutionEngine engine, IBaseTaskExecutionInstance instance, TaskInstanceRequest request)
at Altiris.ClientTask.Server.Execution.ClientTaskEngineExecutionThread.ExecuteTaskHandler()
at Altiris.TaskManagement.Common.Execution.Engine.TaskEngineExecutionThread.OnExecute(Object eventComplete)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
**CEDUrlStart** :http://entced.symantec.com/entt?product=SMP&version=7.1.8280.0&language=en&module=wqSbxPVZRrzOwKHHtkS6m9Pme+vsfHbXV4BHhYwyAj8GNtqF9dn6zCFnU7HWMFvK&error=387333444&build=**CEDUrlEnd**
","Altiris.NS.Security.SecurityCache.get_CurrentIdentityMembership","AtrsHost","70"
I've also noticed in the registry that the following keys do not match
Is this by design? Is a different encryption algorithm used in different places or different hashes used for each?
HKLM\Software\Altiris\Communications\Package Access Password
HKLM\Software\Altiris\eXpress\Notification Server\SW Delivery\DisPoint_Password
Can anyone tell me if theirs match in these two locations?
Re-installing on a clean R2 box again... 3rd times a charm? :D
After completely reinstalling everything, and working through some different issues from the start, we are right back to where we were before with the same error message... "command to get N/W credentials failed"
So it turns out since our ACC account was set to use the app identity and our app identity password contained an unsupported character for the ACC side of things. We changed the app idenity password to not include this character and presto, things work beautifully in DS now!.
Those characters include the following ~!#$%^&(){}
¿Usted tiene gusto de contestar?
Inicio de sesión o Registrar para fijar su comentario.