Hello:
We recently had update our Altiris Server from 7.5 version to 7.6 version. But the clients there are in the version 7.5.
When I tried to push the Symantec Management Agent to my Clients using Altiris Server I received the next error message:
"Failed to push Symantec Management Agent. Error: 1722"
¿ Can you help me please ?
Thanks.
Why are Symantec unable to provide me with the licenses I have purchased through the CTX-exchange program?
Hope someone can help with an issue i am having.
currently in the middle of a patch rollout across an estate of 3000 machines. At least half of these machines are not returning back any success codes or sign that the patches have installed. Many machines are returning a 3010 success code and others after reboot are fully compliant.
The half that are returning nothing at all, when i go and check them they have patched fine, just no inventory data.
Currently funning altiris 7.1 ru 11.
any help or pointers would be much appreciated, first time i have come across this issue.
Hello,
we have 7.5 SP1 HF5 and we need to check whether Agents are able to send events when application start or stop. This application is on shared drive and shared drive is mapped under logged user. Till now we did not find way how to have these events from applications on shared drive. Anybody has idea how to do it?
Thank you
Dear Symantec,
Thanks so much for the fantastic new functionality in SMP 7.6 and especially the new ability to create the adhoc reports in the filters and export the data to CSV files.
Can we please have a button on the report that exports the current SQL used to construct the report into a Classic report for re-use and augmentation? This would also make it much easier to create these reports as well.
Kindest regards,
QuietLeni
Using DS7.5 HF5 to deploy Windows 7 images
After installing the Automation Folder, I am presented with the Windows Boot Loader every time the computer reboots. It has Windows 7 as the default option and the Symantec Pre-Boot enviroment as well and it waits 30 seconds before auto-booting into Windows if no selection is chosen. This is functioning just fine. However, I'd love to bypass the Windows Boot Loader completely and boot straight to Windows so the users aren't presented with any options that could get them into trouble. The only time I want to see any reference to the Pre-Boot Environment is when I queue up a job that requires it.
I'm sure there's something basic I missed. I imagine I could right a script that runs in production and resets the boot device as needed, but that seems a bit clunky. Anybody have tips on how to streamline Windows startup?
When I renew or replace my license, do I need to generate and distribute new clients to my PCs?
Hi
i install SIM 7.6 in Windows server 2012 Standard but when is downloading client management suite(7.5 sp1 and 7.6) fail and sample next error
Symantec Installation manager has encountered a fatal exception and cannot continue:please see the log file for more information
when i was trying uninstall shows the same error
someone can tell me what versions of windows 2012 are compatible with SIM 7.6 and if i can install client management suite 7.5 sp1 with this in windows 2012.
Note:the server is virtual
We held our first in our series of "How-to" webcasts for Ghost Solution Suite 3.0 on March 25, 2015.
Hi,
I'm creating a monitoring project to do some actions in the newest directory on a folder, but I don't know how to get the properties data from a directory. I found the 'Get File Info' component to catch the data, but this component only works with files. Is there any component to catch the created property (or all the properties) from a directory?
Regards,
Hello,
I'm using version 12.1.4013.4013 of Symantec Endpoint Protection Manager for a laboratory environment.
I wanted to know if this version is compatible with SQL Server 2014 Express edition or if SEP has to be updated for it to work.
Thank you.
Hello,
we have two versions of SW, one is for Windows 7 and one is for Windows 8.1 For those we set Applicability rules. In one MSD which is triggered on client we can see that only one Applicability rule is triggered (2 times) and results is Detected even if it is rule for Windows 7 and client is Windows 8.1.
Can you please check it?
Hello all,
I was wondering if anyone finds it very annoying in SD that there are no drop downs for affected user and affected department when creating a ticket. And my real question is, how can we do it? I know customizations are a no-no with Symantec but my CEO is pushing hard for it so I want to deliver.
Any ideas would be helpful
Hi,
We have recently upgraded our Deployment Solution to Version 6.9 SP6.
2300 client machines..all Windows 7 SP1
Agent: 6.9.(Build 648)
A lot of our Dagent clients (Windows 7 SP1) are disconnecting after a couple of hours.
Restarting the Altiris Deployment Agent service, unticking Enctrypted sessions and unticking "Refresh connection" after x hours have had no effect.
The log files on the disconnecting clients are returning the same error:
[04/02/2015 10:56:43.082 3536 2] DsAgent.cpp:968 CDSAgent::Shutdown() - DAgent is shutting down.
[04/02/2015 10:56:43.083 3536 2] DsAgent.cpp:978 - Enter Critical Section
[04/02/2015 10:56:43.083 3536 2] DsAgent.cpp:981 - Inside Critical Section
[04/02/2015 10:56:43.084 3536 2] DsAgent.cpp:990 - Calling ipc->CancelBlockingCall
[04/02/2015 10:56:43.094 3536 2] DsAgent.cpp:998 CDSAgent::Shutdown() - Resetting DAgent Service Event.
[04/02/2015 10:56:43.094 3536 2] DsAgent.cpp:1003 CDSAgent::Shutdown() - Setting Check DAgent Service Event.
[04/02/2015 10:56:43.113 4324 2] DsAgent.cpp:244 CDSAgent::WaitForClose() - Signaling the dispatch thread
[04/02/2015 10:56:43.132 4324 2] DsAgent.cpp:248 CDSAgent::WaitForClose() - Waiting for Dispatch thread to exit
[04/02/2015 10:56:43.134 4324 2] DsAgent.cpp:252 CDSAgent::WaitForClose()) - Signaling the Output thread
[04/02/2015 10:56:43.134 4324 2] DsAgent.cpp:255 CDSAgent::WaitForClose() - Waiting for Output thread to exit
[04/02/2015 10:56:43.146 4324 2] DsAgent.cpp:258 CDSAgent::WaitForClose()) - Signaling the Initial Connect thread
[04/02/2015 10:56:43.147 4324 2] DsAgent.cpp:261 CDSAgent::WaitForClose() - Waiting for Initial Connect thread to exit
[04/02/2015 10:56:43.147 4540 2] UiInitialConnectThread.cpp:76 - Reading initial connect packet.
[04/02/2015 10:56:43.148 4540 2] UiInitialConnectThread.cpp:145 - CUiInitialConnect::ReadConnectPacket.
[04/02/2015 10:56:43.172 4540 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
[04/02/2015 10:56:43.173 4540 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
[04/02/2015 10:56:43.174 4324 2] DsAgent.cpp:264 CDSAgent::WaitForClose()) - Signaling and waiting on the UI Listener thread
[04/02/2015 10:56:43.177 1032 2] UiPipeListenerThread.cpp:176 - CUiPipeListener::Run leaving.
[04/02/2015 10:56:43.177 4324 2] DsAgent.cpp:267 CDSAgent::WaitForClose()) - Signaling the WlogEvent thread
[04/02/2015 10:56:43.178 4324 2] DsAgent.cpp:270 CDSAgent::WaitForClose() - Waiting for WLogEvent thread to exit
[04/02/2015 10:56:43.287 4548 0] apps\dsagent\agent\LogEventThread.cpp:57 - CLogEventThread::Run CLogEventError
Thrown from apps\dsagent\agent\LogEventThread.cpp:113 -message = CLogEventThread::ReadLogEvent() - Shutting down.
SystemError Value = 0x00000000
[04/02/2015 10:56:43.289 4324 2] DsAgent.cpp:273 CDSAgent::WaitForClose() - All threads exited, exiting application
[04/02/2015 10:56:43.322 4324 2] DsAgent.cpp:287 CDSAgent::Destroy()
[04/02/2015 10:56:43.323 4324 2] DsAgent.cpp:293 CDSAgent::Destroy() - Closing socket connection
[04/02/2015 10:56:43.324 4324 2] DsAgent.cpp:304 About to serialize data
[04/02/2015 10:56:43.329 4324 0] DsAgent.cpp:488 About to serialize objects
[04/02/2015 10:56:43.336 4324 2] DsAgent.cpp:307 Deleting queues
[04/02/2015 10:56:43.338 4324 2] DsAgent.cpp:898 CDSAgent::NewMessage()
[04/02/2015 10:56:43.338 4324 2] DsAgent.cpp:803 InvokeHandler called - Internal=MemoryConsumptionOverLimit
[04/02/2015 10:56:43.339 4324 2] TbxDispatch.cpp:40 - Attempting to load default.dll
[04/02/2015 10:56:43.402 3536 0] main.cpp:786 - Leaving Main()
[04/02/2015 10:56:43.403 3536 0] main.cpp:787 - =============================================================
Has anyone an idea what could be causing this?
It is really frustrating.
Thanks..
Regards..
Good day,
We received a request from a software vendor to generate a report of all our machines, and software that are installed on the machine including the path (path).
I searched in Altiris 7.2 and support, but was unable to generate anything that suited the request ..
Here's an example of what we need if anyone can help
Host - Software - Path
Test - Symantec Endpoint Protection 12 - C: \ Program Files (x86) \ Symantec \ Symantec Endpoint Protection
Here also we have so far, without the path
SELECT DISTINCT comps.Guid [Guid]
,comps.Name [Computer Name]
,prods.[Name]
,spv.[Version]
,company.Name [Company]
FROM vRM_Software_Component sc
JOIN Inv_InstalledSoftware inst
ON inst._SoftwareComponentGuid = sc.Guid
AND inst.InstallFlag = 1
JOIN (SELECT ra.ChildResourceGuid, spi.Guid, spi.Name
FROM vRM_Software_Product_Item spi
JOIN ResourceAssociation ra
ON ra.ParentResourceGuid = spi.Guid
AND ra.ResourceAssociationTypeGuid = '9D67B0C6-BEFF-4FCD-86C1-4A40028FE483'
)prods
ON prods.ChildResourceGuid = sc.Guid
JOIN dbo.Inv_Software_Product_State sps
ON sps._ResourceGuid = prods.Guid
AND sps.IsManaged = 1
JOIN dbo.Inv_Software_Product_Version spv
ON spv._ResourceGuid = prods.Guid
JOIN (SELECT vci.Guid, vci.Name
FROM vRM_Computer_Item vci
LEFT JOIN ResourceAssociation resAssoc
ON vci.Guid = resAssoc.ParentResourceGuid
AND resAssoc.ResourceAssociationTypeGuid = '3028166F-C0D6-41D8-9CB7-F64852E0FD01' --Asset Status
WHERE (resAssoc.ChildResourceGuid = '0A0203A5-D2B6-49f1-A53B-5EC31A89437C' OR resAssoc.ChildResourceGuid IS NULL) -- ONLY Active Computers
) comps
ON comps.Guid = inst._ResourceGuid
LEFT JOIN (SELECT ra.ParentResourceGuid AS softProdGuid, rc.Name
FROM RM_ResourceCompany rc
JOIN ResourceAssociation ra
ON ra.ChildResourceGuid = rc.Guid
AND ra.ResourceAssociationTypeGuid = 'D5C66D5A-7686-4CA2-B7C1-AC980576CE1D'
) company
ON company.softProdGuid = spv._ResourceGuid
ORDER BY prods.Name, comps.Name
Making Ghost WinPE / Vista 32-bit to work with Intel i217-lm chipset.
By Terry Waskowich
First: This is not a Symantec supported solution.
Do Not call Symantec for support with this solution. Use at your own risk... But it works!
A fellow IT colleague on campus came and asked if we experienced communication issues with Ghost Console Suite 2.51 and Dell 9020/7020 computers.
I was asked to help them and find a solution. The colleague was adamant that there was no solution available.
After looking on both the Intel and Symantec forums to find they also acknowledged there were no solution available.
After some days working on this here and there, I downloaded the I210 driver set for Vista and modified the .inf to recognize the Dell 9020 i217-LM Network Adapter Hardware Id of PCI\VEN_8086&DEV_153A&SUBSYS_05A41028. Vista 32-bit loaded the driver set and received an IP address.
I used Vista 32-bit since it was quicker to load up driver sets than recreating the Ghost WinPE image or having to reboot Ghost WinPE when manually loading a driver set would not give me a proper result. Every post I read stated that if the drivers work under Vista 32-bit then they will work under Ghost WinPE.
Unfortunately this was not the case here. Ghost WinPE recognized the hardware but the driver fails to actually load in the bootable WinPE environment and resulting in no IP of course. Ipconfig.exe would only show one line : “Windows IP Configuration”. Ghost app shows an IP of 127.0.0.1 .
I started to look at this another way and searched for other intel chipset (with similar release years) that had issues with Vista. Found a post describing Vista 32-bit issue with a different Intel NIC. Downloaded the posted.sys file, renamed it and now the driver set works in both Ghost WinPE and Vista 32-bit.
Unfortunately posting a modified .inf and a nic driver .sys file that was pulled from an unkown source might be against Intel’s “materials” agreements.
So after some hard looking, the nic driver .sys is actually on Intel’s own site; believe it or not. (I did a MD5 checksum compare to find it).
Here are the instructions on how to create your own driver set for the I217.
After reading the following I feel embarrassed on how quickly this should have been accomplished before.
I would like that thanks the guys at https://communities.intel.com/thread/43218?sr=stream for starting the thread.
Thanks for kamouille on the intel communities for his comments.
--------------------------------------------------------------------------------------------------------
How to get the I217-LM to work in Ghost WinPE 32-bit (Vista 32-bit too).
1) Download the Intel 18.1 CD contents from http://downloadmirror.intel.com/22641/eng/18_1_CD.zip
*You can try other versions of Intel CD sets, but some will not load and the result is an IP of 127.0.0.1.
2) Extract the .zip file to your computer (eg: c:\)
3) Edit the e1r6032.inf file as follows: (thanks kamouille)
e1r6032.inf file from folder c:\PRO1000\Win32\NDIS61
in the [Intel.NTx86.6.0.1] section and this one line:
%E153ANC.DeviceDesc% = E1533.6.0.1, PCI\VEN_8086&DEV_153A
in the [Strings] sections add this one line:
E153ANC.DeviceDesc = "Intel(R) I217-LM Gigabit Network Connection"
(optional for W2K8)
in the [Intel.NTx86.6.0] section Just have this one line:
%E153ANC.DeviceDesc% = E1533, PCI\VEN_8086&DEV_153A
4) Save it!
Now you might have to add the &SUBSYS_05A41028 (This is from a Dell 9020) to the end of the PCI\VEN_8086&DEV_153A lines above.
This additional information can be found within Windows Device Manager.
Using Device Manager find the i217 Network adapter, go into the Properties and then under Details tab select Hardware Ids from the dropdown menu.
Some NICs need their &SUBSYS_xxxxxxxx information to load the driver properly.
You are Done. Now add that driver set to your Ghost Solution Suite WinPE via GSS Boot Wizard and enjoy not needing to walk to each machine!
--------------------------------------------------------------------------------------------------------
*** Now if you want a cleaner driver set do the following but only after the above modified driver set has been tested to work.
1) Edit your new modified e1r6032.inf and
remove all other entries under [Intel.NTx86.6.0.1] section so it only shows this one line.
%E153ANC.DeviceDesc% = E1533.6.0.1, PCI\VEN_8086&DEV_153A
(optional for W2K8)
remove all other entries under [Intel.NTx86.6.0 section so it only shows this one line.
%E153ANC.DeviceDesc% = E1533, PCI\VEN_8086&DEV_153A
2) Save it!
3) Copy the following files from c:\pro1000\win32\NDIS61 to c:\i217
e1r6032.cat
e1r6032.din
e1r6032.inf
e1r6032.sys (MD5 checksum value : 31f6fd7d6013b2f713142ee6d627f935)
e1rmsg.dll
NicCo26.dll
NicInE1R.dll
PROUnstl.exe
I prefer this way since most IT techs have only one Ghost WinPE setup and this will prevents overlapping of driver sets that may have the same intel hardware Ids in the .inf file.
I hope this helps you all! This has confirmed to work on Dell 7020, 9020 and 9030 models. Worked on an HP Laptop with i217 as well.
* Please note there are no storage device driver for the Dell 7020 built into Ghost.
I will soon write up the how to make your own Dell 7020 compatible driver set for Ghost Winpe.
Terry Waskowich
When building a software package, you can select the option to have software management framework generate command line for you. This works wonderfully for .msi files and gives you a few different options to choose from, multiple install commands and uninstall commands. Can command line options be integrated to generate for .msu files so that we don't have to continue using custom options?
Last I heard, Symantec is sticking by their decision to keep the CMS interface in the browser versus an app (and IE only to boot). I wonder if any thought is given to improving the interface, especially with IE not likely to get much improvements once "Spartan" comes out.
Our Mac management system is browser based as well and it is so much more efficient to use (albeit they don't try to promise drag and drop which I think hinders the Symantec console).
For example, I'd like to move about 100 old patch policies into a folder. Right now, I'm not aware of a way to do this efficiently (am I missing something?). Drop and drag doesn't work reliably. So I have to right click on each policy and select Move, navigate the folder structure, select the folder, click ok. To move 100 policies, I bet it will take me a few hours. I give up after 15 or so just out of eye strain or distraction from other task that comes up.
If instead things like checkboxes were used, where I could select 100 items, then have a way to do a move operation, it would probably take 2 minutes to move 100 policies. Checkboxes could be used for static filters and probably some other items as well where you just want to quickly select items and do a mass task on them.
Here's another idea I had for improving the interface making links in lower left customizable
I'd love to get a thread of ideas together if there was a chance any of them would make it into the future product.
I reviewed this post http://www.symantec.com/connect/forums/how-do-you-create-pie-or-graph-charts-altiris-71-reports
And that is the basics. But when I select Pie chart it only shows one of my attributes.
I am using this query:
SELECT
IPAD=(SELECT COUNT (*)
FROM vAsset
WHERE [Asset Type] LIKE 'ipad' And Status like 'Active'),
Blackberry=(SELECT COUNT (*)
FROM vAsset
WHERE [Asset Type] LIKE 'blackberry' And Status like 'Active'),
[Mobile Device]=(SELECT COUNT (*)
FROM vAsset
WHERE [Asset Type] LIKE 'Mobile Device' And Status like 'Active'),
Aircard=(SELECT COUNT (*)
FROM vAsset
WHERE [Asset Type] LIKE 'Aircard' And Status like 'Active')
If I try and do a Column chart I cannot get it to show all the columns. I tweak it and preview and it looks good, but after save it goes back to 1 column or no columns. Is anyone experiencing this as well?