Install Symantec System Recovery 2011 Manually

Problem Attached to this document are the latest FIXINSTALL.BAT and UNINSTALL.BAT files for Veritas System Recovery 2011. Solution CAUTION: Please use 'Add or Remove Programs' or 'Programs and Features' control panel to uninstall products, uninstall.bat can be used only if trouble or issue occurred during uninstall the product. Running uninstall.bat without performing uninstall by 'Add or Remove Programs' or 'Programs and Features' control panel might leave unnecessary files or registry keys on the system.

• Symantec System Recovery Disk

NOTE: uninstall.bat does not remove the recovery point files and its folders, and VProRecovery folder(s) on the backup destination machine. Please remove them manually if unnecessary.

The attached files can be used to repair an existing install, or completely remove SSR 2011. To completely uninstall SSR 2011:. This uninstall batch file is meant to uninstall the 'Veritas System Recovery 2011' product only on 32-bit and 64-bit operating systems. Download UninstallSSR2011.zip and extract to the C: root directory.

2 files will be extracted: UninstallSSR2011.bat and LUReg.exe. Both files must be in the same location in order for the uninstallation to occur. Open a command prompt and navigate to C:.

Run the following command from Windows Command Prompt: For 32-bit. Systems: UninstallSSR2011.bat -I 'C: Program Files veritas veritas System Recovery ' For 64-bit. Systems: UninstallSSR2011.bat -I 'C: Program Files (x86) veritas veritas System Recovery '.If you modified the installation path of SSR during the original install, modify the command above to reflect that same path. Confirm that the folder is still present in the command line. If not, create a new empty folder in that location with the name Veritas System Recovery. The uninstall cannot complete without this folder in place. Reboot the system.

SSR 2011 is now completely uninstalled. To repair an existing install of SSR 2011:. Download SSR2011Fixinstall.bat to the following directory, overwriting the existing file if prompted. Rename the file from SSR2011Fixinstall.bat.txt to SSR2011Fixinstall.bat: Windows Vista 7 2008: C: Program Files (x86) veritas veritas System Recovery Windows XP 2003: C: Program Files veritas veritas System Recovery. Right-mouse click on the file and choose Run As Administrator. A command prompt box will open while the file runs and will close when complete.

Reboot the system. The repair of the SSR 2011 installation is now complete.

Last week I had to uninstall Symantec's Backup Exec System Recovery (and Endpoint Protection) because it seemed to be causing some problems with another software program. This was no easy task since Windows could not uninstall it, Symantec would not help me (except for a $250 fee) and the manual method was pretty tedious. I now am trying to reinstall BESR and after it goes through all its setup/copying stuff and I then reboot, when it comes up and I try to continue the installation I get the message 'E1AD3212: You do not have sufficient privileges to perform this operation.' I tried running the installation as administrator (evern though I am always logged on as an administrator anyway) but that made no difference. Googling around, I found an article that supposedly addresses this problem and says:. To resolve this issue: Add the logged on user to the Security Configuration Tool: 1.

Click Start  Programs  Symantec  Security Configuration Tool 2. Click on 'Add.'

Click on the logged on user account and add it to the Security Configuration Tool. Restart the Backup Exec System Recovery Agent Service: 1. Click Start  Run 2. Type in 'services.msc' without the quotes 3.

Right click on Symantec Backup Exec System Recovery service and select 'Restart'. So I added myself and 'administrators' and even 'users' to have full control. In services.msc BESR wasn't running and so I just clicked on 'Start' but got the message that 'Windows could not start Backup Exec System Recovery on the local computer.' I also found some articles at MS and elsewhere that said that perhaps Micrfosoft.NET Framework Version 2.0 might be the culprit and recommended uninstalling/reinstalling that. Well, MS.NETv2 is not on my system (Vista) that I can find. I thought, well, I'll reinstall the Version 3.5 that I did find.

Windows would not let me do that either. I also found a web page that said: 'Check DCOM Settings at, there is a document that will assist with setting DCOM. The same users as above should be in DCOM also.' But the link took me to Symantec Knowledge Base where it said: 'We're Sorry.

An error has occurred in the Symantec Knowledge Base. You may have accessed a document which is no longer available or attempted to open an invalid document.' I know nothing about DCOM so I just stopped persuing that. If I didn't have so much invested in Symantec's products on our eight computers, I would abandon them completely. It seems at every turn we are having some sort of problem with their software or other software caused by their software.

Anyway, I just don't know where to go from here to get this installed. I'm wondering if the uninstall I performed didn't actually get everything off my system so there is some sort of conflict between the old an new installation. Although I was sure that I turned UAC off a long time ago, I checked anyway in ControlPanel UserAccounts and verified that it is indeed turned off. I'm not familiar with the Security Event Log but opening the Event Viewer, I only get the message: 'Event log service is unavailagle. Check that the service is running.' I went into Services.msc and found two possibly related items: 1.

MRService, which I right-clicked and Restarted. Windows Event Log; which was not running but when I selected Start, I was told: 'Windows could not start the Windows Event Log service on Local Computer - Error: 4201: the instance name passed was not recognized as valid by a WMI data provider.' I was able to start the Windows Event Collector which I saw was mutally dependent with the Windows Event Log.

Symantec System Recovery Disk

I seem to have gotten past the problem. I found some clues at and, although the problem presented was not identical, following the steps to get some security settings back in line did the trick. It said:. I have fixed this problem. It was related to Windows Event Log service that Norton Ghost is dependent on.

The fix is discussed here: Here is a post that mentioned the fix: Begin quote GOOD NEWS PEOPLE!!! I finally solved my Ghost 12 problems. It was after a failed uninstall that would not complete probably because I had altered the Owner and permissions. I then used jv16 PowerTools 2007 to remove the program which it did, and then I used it again after rebooting to clean the registry of errors. Then I reinstalled Ghost 12 using the Repair function of the Ghost installer. I had to do this because I think the Windows Install Shield still thought that Ghost 12 was still installed.

After the successful install I rebooted the computer and a window came up that showed: Cannot connect to agent on computer ELMER-PC, but I was glad that I had gotten past the 'Welcome to Norton Ghost' screen. I then checked out the Ghost Help file in the program, and it stated in troubleshooting that the Windows Event Log in Windows Services must be enabled and started for Ghost to work. I tried to start the Event Log but I received a Windows error message stating that it could not be started.

I searched in the web and found this solution posted by Geircito on the TechArena Community forums: Here's the solution: Something (Vista itself??) must have changed the ownership of the LogFiles folder. How to take ownership: Open folder C: Windows System32 Right click folder 'LogFiles' - open Properties open Security-tab and click Advanced open Owner-tab and click Edit mark Administrator (or your user) under 'Change owner to:' mark 'Replace owner on subcontainers and objects' press OK and press 'Continue' to all error messages close all open windows restart your PC, and the Event Log Service will restart automatically Well my computer was showing the right Owner Administrator/Elmer-PC, but I did put a check by 'Replace owner on subcontainers and objects. I did receive a couple of error messages so I thought this was not going to work, I then restarted my computer and to my surprise Norton Ghost 12 started as it should! I hope this thread can help someone if they experience the same problem as I encountered.

end quote However, I had to do extra steps below to fix Windows Event Log service: Navigate to C: Windows System32 LogFil es WMI RtB ackup Right-click on RtBackup and select Properties  Security In the list of Group or user names is SYSTEM listed? If not, click Edit  Add. And type in SYSTEM in the dialog box and click OK. Restart your computer and try installing Windows Vista Service Pack 1 again. The above steps were discussed here:.