Problème de deploiement d'agent sur un poste client en XP SP3
Bonjour Jai installé la version de SSR 2013 R2 sur un poste en Windows 7 jai deja realisé des deploiements d'agents et sauvegarde sur des postes clients surwindows 7 par contre quand je veux installer l'agent sur des postes en windows XP cela ne fonctionne pas je n'ai pas de message d'erreur sur la console comme si tout c'etais bien passer ,par je retrouveaucun repertoire Symantec sur le poste clientquelqu'un peut m'apporter une réponse merci
Agent not communicating on server with domain controller
Hello. I have several 2003R2 servers that I'm looking to backup with SSR 2013R2 Server. I have one main server that contains SSR and have installed the agent to multiple servers on the network with no issues being able to comunicate back and forth to them. I'm having an issue with one of them though. It's our DR domain controller server. I'm able to deploy the agent to the server with no issues. After the server reboots, I can no longer connect via SSR. I can see it in the list of computers and it shows the agent is installed in SSR computer search but I can't do anything else with it. Any ideas?? Thanks
Symantec System Recovery 2013 R2 Authentication Issue with NAS
Hi, I imagine this question has already been addressed before but Google / Bing searches have lead me on a wild goose chase, so I'm posting this question here in hopes of an easy resolution. We're using Symantec System Recovery 2013 R2 and we just installed a new Qnap NAS. The environment is mixed Win7 / Win8 and some of the SSR clients have no issue authenticating with the NAS so that they can store backups there. Roughly 35% of the client machines, though, can't authenticate correctly, no matter what login I use (e.g. domain\username : password, localusername : password, etc.). Since it works on most of the machines, I feel confident my domain accounts and local accounts are setup correctly. I even synced the passwords temporarily so I could side step the possiblity of a mistyped password. The clients that won't authenticate with the new NAS will authenticate with an old failing Lacie NAS with a default local account of admin : admin, but they simply fail with every account I've tried with the new NAS. I can't detect anything different between the windows 7 boxes that fail and the ones that suceed (same with the Win8 boxes). Any clues would be appreciated, since I need to clean up our backup architeture as soon as I can. Thanks.
Reparing SSR 2013 R2
Hello, Recently I found a reparing process in SSR, which is not proposed in the users'book ! Last two years, with Windows 8.1,Iwas suffering many troubles with the SSR Agent (if the computer remains unused during two weeks or if you change a hard diskwhicharrives out of order). SSR says something like: "Connexion failed ..."; "Can't spread out the agent ..."; "Incorrect user's name or user's password". Recently Iam on the point to throw SSR to the garbage can, but as an ultimate effort I decide to reinstall the same SSR versionon the preceeding (without deleting the existing version). Of course a comment arrives: "You can't install two exemplaries of SSR ...". OK; The interesting fact arrives after a while: a window with two items; -1- repair SSR - Menu2- reinstall SSR. I select "Repair ..." .The repairing process takes place with the usual two progression bars and SSR is launched successfully with my personnal configuration ! Conclusion: 1- very likely in some cases the SSR agent is desactivated. Unfortunately SSR don't give any valid way to reactivate it. You have to consult the user's notice to find how to reactivate it in the Windows Services Menu. 2- I was not aware of the existence of any repairing process in SSR ! How to find the Windows Service Menu with Windows 8.1: under MUI type anywhere "Services" and click on Services. On the list which arrivesselect, near the bottom "Symantec System Recovery". At the upper left cornerit appearsa SSR service description, and two items: Activate, Desactivate. Good luck ! MR:-)