Unable to connect to Remote Agents in BESR 2010
This does not happen to all of the computers I try and connect to, just the newer models ones. I have been deploying the 2010 agent from my computer to remote PCs and up until now, I have had no problems. When I try to connect to a remote computer that is giving me problems, it asks for network credentials. No matter what I put in it will not let me connect. However, I can deploy the agent to the machine, but after that I can not connect to it to manage it. This has only been happening on newer machines, If we reimage the machine then most of the time it will start working. Sometimes we have to reimage it two or three times. Any ideas? I just find it strange that this only happens on our brand new machines. They are all running XP Pro. Below is an image of the message I receive when trying to connect.
How to Rid the Registry of Altiris ?
I have 35 systems with which I installed the Altiris Agent, BESR Plug In, and BESR 2010 through the (Altiris) Management Solution console. For a number of reasons I want to dump the Altiris Management Solution and manage these systems individually as standalone BESR 2010 installations. As part of the ensuing uninstall/reinstall process I want to completely remove all Altiris entries from the registry – and there are hundreds of them. When installing the Altiris agent via policy from the Management Console there is the option to install it such that it creates an entry in Windows Add/Remove Programs. I did not notice this till after most of the client installs were completed. However, even when using this option,the Altiris registry entries are not removed. Elsewhere on the Symantec web site I have seen the following steps given as the recommended way of removing the Altiris agent; Run the following command line to remove the Altiris Agent using AeXAgentUtil.exe located by default at C:\Program Files\Altiris\Altiris Agent\AeXAgentUtil.exe /uninstallagents /clean (*) Delete the following Program Files folder if still present: C:\Program Files\Altiris\Altiris Agent (**) Delete the following Registry key if still present: HKLM\Software\Altiris However this does not begin to remove all the registry entries. So, does Symantec provide a way to efficiently and completely uninstall their product? Specifically the Altiris agent registry entries.Former Ghost 15 user - Getting trapped in the SSR 2013 Trial
A few days ago I had an issue with doing a system restore using Ghost 15. I went to that forum for help and learned that Symantec was going to discontinue Ghost and recommended users "check out" SSR 2013 with its free trial. I downloaded the free trial and eventually learned it would not install unless I first remove Ghost. That wasn't from anything that I saw when the SSR installation failed; that happened without any additional information. However, I did eventually find my way to this forum and a helpful Guru pointed out the issue and also that I could always re-install Ghost if I wasn't happy with SSR. I uninstalled Ghost, installed SSR, and started backing stuff up. Now, if one of the things you want to do is a full system restore (my primary interest)then you need a recovery disk. SSR will make a recovery disk for you and all you need to do is provide an activation key which you don't get with the trial version. No problem, as all I need to do is install Ghost. But I can't install Ghost until I uninstall SSR. And SSR WILL NOT UNINSTALL. Whenever I try to uninstall it there's an Error 2738 and something about a VBasic error. So now I have a trial verision of a program that I can't use and a paid for program I can no longer load. I guess it can all be fixed if I pay Symantec for an activation key for a program that I'm not sure I want in the hopes it will maybe allow me to upgrade to a latter version that can uninstall so I can install the program I uninstalled so I could evaluate the Free Trial. To put it another way, I may have to pay Symantec to I can remove their free software and load back the software I paid them for as well. And, even it it turns out there's a simple, and hopefully less expensive, way out of this I've still wasted a lot of time on what should be a free trial of a comercial product which appears to be more of an alpha test. (If I sound upset, it's because I really am)
Active Directory Server (Windows 2003 R2) unable to boot after Installing Symantec System Recovery 2013
Hi Everyone, We successfully deploy SSR 2013 on Windows Server 2003 R2 but problem arised when we try to deploy it on an Active Directory Server. After successful installation, the server requires a reboot. But when we reboot it, the server failed to boot on Windows. What we do is to uninstall the SSR 2013 so that it can boot properly. We try other vesion of SSR like 2011 but same error occurs. The credential we used on installing SSR has an administrator rights. I would like to know if SSR 2013 and 2011 has compatibility problem on Active Directory and what we can do to fix it? Thanks in advance..:)