hi,
I have this message when I deploy windows7
"ErrorMessage: Exception has occured in File Tcube_ClientImageDeploy.cpp at Line No 903. Type of exception is ClientImageDeployException. Error Description is Child Process returned an error. The exit code from process is 1. Value of Windows error code = 1"
But when i deploy Windows8 its walking very well
need help plz
I need to pull a report showing installed applications on all my end point devices. I'm currently runnning Altiris 6.9 and I cannot figure out how to do this.
Can DS6.9 sp6 image the PC300 NVMe SK Hynix SSD? I'm just trying to image Win7, not Win10?
Both Ghost and Rdeploy cannot image to the drive, rdeploy cant see the drive and Ghost errors out that the drive does not have enough space.
Thank you for any help!
Earlier this week I created a new Windows 10 image using ITMS 8 HF4. I then found, after deployment, that no software deployment tasks would run in production. I found that after upgrading the server to HF6 these tasks worked correctly.
So I fired up my template Windows 10 VM, updated its image to include the HF6 agent and plugins and then prepare for image capture, rebooted to PXE and captured the image.
However the job never actually completes. The files get created on the server and Ghost shuts down but the tasks in the console never completes. Looking through the server logs I can see that occasionally the tasks "wakes up" but still never completes. The new image is not accessible or listed in the GUI so cannot be deployed.
Has anyone else seen this?
Howard
I am trying to get the automation folder to rebuild itself and for some reason no matter what I do will cause it to rebuild
I can get the PXE configuration I created to rebuild just fine, but the automation folder just stays at the original that was created when I first installed 8.0
Suggestions on things to check?
I have created a new configuration with another automation configuratoin and that won't build the exe at all?
Hello,
We are using ITMS 7.6 HF6 as well as CEM. I have a unique situation where I may have a need to image machines outside the network firewall. Is there a way to add the Cert to WinPE (on a boot stick) given the CEM package server and the client has the network bandwidth?
I am open to suggestions if this might be possible.
Thanks!
Hi all
We have installed SEP management console on a new server recently and we need to push new client to computers (which is about 4000 computers). The problem is network bandwidth. We are not able to deploy clients to multiple machines. (for me i am doing it one by one which makes me lose significant time and sometimes deployments fails because of this network problem). My question is, Is there a way to deploy the exe file to a machine and then make other machines get the package from that machine?(not from the management server).
Thanks in advance
Recently I have noticed that "Retired" computers, or computers that have been purged based upon the fact that they have not checked into the database for 'x' days, will not recognize their task server while in WinPE.
In our imaging process, we use the %taskserver% token to determine where the machine should pull the image from. If a machine is "retired" given the above criteria, that value is blank. The only way around this issue is to delete the machine from Altiris and restart the imaging process. This removes all history from the DB and we don't necessarily want to do this.
Due to licensing constraints, we cannot remove the automatic purging, nor can we increase the time constraints in which a machine has checked in.
Any insights would be appreciated.
This is for Windows 10 LTSB.
We installed Windows 10 LTSB and I am not sure if it's actually Windows 10 LTSB or if an update broke the package, but it appears we can't install this plugin.
The agent gets the install and it downloads it just fine, but it appears that after it tries to install...it doesn't show up and it appears it's not installed.
These are the plugins that are installed even after doing the install/upgrade to see about getting it to work.
Altiris Base Task Handlers 8.0.3396
Altiris Client Task Agent 8.0.3396
Inventory Rule Agent 8.0.3396
Software Management Framework Agent 8.0.3396
Symantec Management Agent 8.0.3396
This is from the run history.
3/13/2017 6:21:59 PM Run completed asynchronously 0 DOMAIN\someuser1 SYSTEM C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\{80862EA5-B80E-422F-A9C1-2B5BD00E8473}\cache
I have 8.0 HF6. Everything was running smoothly, until last night, when the server had a sudden reboot (the server room UPS and top-of-rack switch are rubbish and being replaced as I speak, and keep causing server reboots).
The log is showing the following over and over:
Operation 'Direct: Post' failed.
Protocol: HTTPS
Host: psy-deploy.dept.example.edu:443
Path: /altiris/NS/Agent/PostEvent.asp
Id: 39.5980
Error type: SMP Server error
Error code: Catastrophic failure (0x8000FFFF)
Error note: HTTP Status 200: 200 OK
Trying to restart Altiris Service gives me this
My first thought is to blow out and reinstall the whole server--which really doesn't take that much time compared to the hours I'd spent putzing around in unfamiliar waters.
That having been said, if the Web console won't work...how can I use ImportExportUtil to export the Job/Task menus? That's all I really need to restore if I rebuild the server...the existing Symantec Management Agents in the field will automatically relocate the server.
Thoughts?
Thanks!
Hello everyone.
I've been trying to get a simple deployment solution to work for quite a while yet.
After clearing a lot of hurdles, I've hit a roadblock I have no idea how to solve. Right now, I install Windows ADK, create a configuration with Bootwiz, edit the startup.bat to mount a pair of additional network drives and map a costum static IP to a machine. Everything works great, and it connects to the server just fine. Even receives commands and deployment tasks.
The problem is that it only boots into automation if I run the automation folder installer. Everytime I run it, it prompts me to reboot my computer, which it happily does without further input and proceeds to load Windows PE. But when I return to production, the automation folder doesn't show up on MSCONFIG. It doesn't appear in the boot menu. And when I send a task to the client that requires booting to automation, it fails to do so.
I've seen two odd things so far. A few days ago, when I couldn't even connect to the server, the installer would create a hidden "boot" folder in C:\ where the wim file was placed along with what I think is a costum bootmng. Now, after the automation installer runs, the folder isn't created. It still boots to automation, but I have no idea what's happening and allowing it to so.
Secondly, when I do boot into automation, I used to be able to see two extra drives. C: would be a 100 mb with a bootmng for windows, while D: would be the normal C: drive I get in production. Windows PE would boot into X:. But right now, C: is a 300 mb drive called "BOOTWORKS". It seems to be the "embedded partition" because Windows PE still boots into X:, the RAM temoporary disk. I can't see the other two drives anymore.
I have no clue about what changed this. It seems it's ditching the "automation folder" and going back to "automation partition" from previous versions, but I'm still using GSS 6.8 as far as I can tell. I tried searching the forum since I've previously found solutions for all other problems, but I didn't see anyone with this problem.
I'm looking to create a process where a hard drive is backd up into a .gho file for one of two purposes:
This having been said, I'm looking for something dump simple that doesn't require touching the hard drive. I was thinking of this:
When I do this, I get this:
ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in function SMPPackage.cpp() at Line No 233. Type of exception is GeneralError. Error is callDSPSInfoOperationService()have failed. Return XML is =. Error from HttpGet = A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. Error Description is utilCSMPPackagecallDSPSInfoOperationService. Value of Windows error code = 6 and message is The handle is invalid.
Thoughts?
Thanks!
I created an image and have an older image that I use for the PCs. (Mainly dell computers.) Here recently I can not get the PCs to boot to the image. It just says selected boot device failed. I tried messing with legacy and uefi modes and can't seem to get anything to work. What I bothers me is that it worked fine on on all dell computers and now it doesn't at all.
Any ideas what I can check? Thanks
Deployment Solution 8.1 documentation is available at the following URLs:
All user guides and release notes of IT Management Suite 8.1 solutions and components are available at the following URL:
Hi Team,
What is size of client package from SEPM 14.1 to SEP 14.1 client. and what is method of upgrade for future clients.
I am trying upload all drivers into the DriversDB for DeployAnywhere. With the WIndows x86 drivers for Optiplex 5040 and Latitude E5530 (for now) I am having trouble uploading the Intel Management Engine Interface Drivers (MEI/HECI). Message is "Failed to import driver: -Driver Path on NS- [Failed to find any drivers to add.].
I had this also with some biometrics drivers, resolved it by taking files from the driver's sub-directory and moving them to the driver's parent directory. I am aware that the DA DriversDB needs: .inf/.sys and if I am correct .cat files in order to upload at all to the DriversDB. But with the MEI drivers if I complile all files into one directory it still fails to upload.
See attached capture files for the import failure message and the files for the driver.
Not sure this is relevant, this is in my test environment and it is running Symantec CMS 8.0 HF3.
Hello
We trying to capture image in DS 7.6 after long time. As per best practice we get new job for image capture and below task
1) Prepare for image capture
2) Create Image
3) Boot to Production
Its failed in Create Image. Below is error
ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File Tcube_ClientCaptureImage.cpp at Line No 834. Type of exception is ClientCaptureImageException. Error Description is Child Process returned an error. The exit code from process is 1. Value of Windows error code = 6 and message is The handle is invalid.
Upon enabling Enable Mac Netboot(BSDP) support Network Boot Service goes into a critical error state:
Service status:Error
Service message:The system cannot find the file specified.
The preboot enviroment was created under Preboot configurations and uploaded. I can see that it replicated to all site servers. Disabling BSDP fixes the issue. Besides burning the Apple devices, any ideas? Thank you!
8.0 HF6
I have a Create Image job that appears to have successfully made an image of the drive (the Ghost window showed up, and the .gho files are now on my server)...however, the job itself failed at 99 min:9 sec with this:
ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File Tcube_ClientCaptureImage.cpp at Line No 877. Type of exception is ClientCaptureImageException. Error Description is Child Process returned an error. The exit code from process is 1. Value of Windows error code = 2 and message is The system cannot find the file specified.
Thoughts?
Thanks!
I just upgraded from 8.0 HF6 to 8.1. The agent upgrade went smoothly, but now booting into WinPE fails...
SMP.log:
<event date='04/17/2017 08:52:32.5200000 -08:00' severity='4' hostName='minint-3pfitgj' source='PectAgent' module='PECTAgent.exe' process='PECTAgent.exe' pid='1648' thread='1652' tickCount='32671'>
<![CDATA[Version 8.01.4536]]>
</event>
<event date='04/17/2017 08:52:33.2230000 -08:00' severity='1' hostName='minint-3pfitgj' source='PectAgent' module='PECTAgent.exe' process='PECTAgent.exe' pid='1648' thread='1652' tickCount='33375'>
<![CDATA[AgentGlobals.h:110 Agent Exception, Could not laod file ErrorCode=0, SystemError=6]]>
</event>
PectAgent.log:
[2017/04/17 08:52:32.520 1648:1652 2] Log File Created. Version 8.01.4536
[2017/04/17 08:52:33.114 1648:1652 2] AgentGlobals.h:135 RegisterLibrary: x:\program files\Symantec\Deployment\Client Task Agent.dll has been registered sucessfully
[2017/04/17 08:52:33.207 1648:1652 2] AgentGlobals.h:135 RegisterLibrary: x:\program files\Symantec\Deployment\AeXNetComms.dll has been registered sucessfully
[2017/04/17 08:52:33.223 1648:1652 2] AgentGlobals.h:108 RegisterLibrary: LoadLibrary Failed to load x:\program files\Symantec\Deployment\AeXBasicInventory.dll
[2017/04/17 08:52:33.223 1648:1652 0] AgentGlobals.h:110 Agent Exception, Could not laod file ErrorCode=0, SystemError=6
[2017/04/17 08:52:33.223 1648:1652 2] PECTAgent.cpp:160 Stopping PECTAgent. Please check for Network configuration or server name resolving problem and try again.
Thoughts?
Thanks!