System Recovery 2013 R2 SP3
Hi, SP3 for SSR 2013 seems to be out since July, but still it does not show up in Live Update. Is there a reason for that? Thanks in advance! Tim P.S: Also, if somebody could enlighten me regarding posting to this forum. My posts are encircled by a dotted red line and are marked "unpublished". Somehow days later they are automatically published. I must do something wrong. Thanks (written 10/07/15)
symantec system recovery 2013 backup script failed to run
Hello ALL, I am running CreateImageNow.ps1 from the cygwin and its gives error . I tried to run the script form different system (2-3 system) only on 1 system it runs succesfully .Scipt is also attached & Error is pasted below : I need the solution ASAP . Any kind of help is appreciable . $ powershell.exe -inputformat none -noprofile -File CreateImageNow.ps1 //192.168.125.34/test101_v_0_FS_0 E:\\ //192.168.125.34/test101_v_0_FS_0 --> destination where data is backuped E:\\ -> drive which need to be backuped. connecting... Failed to Connect with an Exception... System.Management.Automation.MethodInvocationException Exception calling "Connect" with "1" argument(s): "" Exiting... $ powershell.exe -inputformat none -noprofile -File CreateImageNow.ps1 //192.16 8.125.34/test101_v_0_FS_0 E:\\ Connecting... Failed to Connect with an Exception... System.Management.Automation.MethodInvocationException Exception calling "Connect" with "1" argument(s): "" Exiting...
Unable to See Symantec System Recovery 2013 SP2 in SIM
Hi, I wish to update the version of our Symantec System Recovery Management Solution 2013 to the latest version which I believe is SP2, however after Updateing the product listings in Symantec Installation Manager (SIM) I can only find SSRMS 2013 SP1. Has SP2 been released for users of SIM? I know it is available directly from Symantec. Many Thanks.
Symantec System Recovery 2013 Desktop Edition and Windows 8.1 compatibility
Symantec software development employees for "Symantec System Recovery 2013 Desktop Edition": I have SSR 2013 Desktop Edition version 11.0.1.47622 right now. I am upgrading from Windows 8 to Windows 8.1. I much prefer to have system image backup/restore software (like SSR 2013 Desktop Edition) as an insurance policy at all times. Unlike with Windows 8, I understand that SSR 2013 Desktop Edition will NOT work with Windows 8.1. When you try to restore a partition using the System Recovery DVD disc it fails. I wasn't too pleased to hear about this at all. I have read on the internet that Windows 8.1 was not reallya major OS update. Is Symantec going to provide a new version of SSR 2013 Desktop Edition (like 11.0.2.XXXXX) in the next week or so that fully supports Windows 8.1 partition backups/restores? That would be awesome if Symantec could do this. In order to backup/restore Windows 8.1 partitions, is Symantec going to make all the SSR 2013 Desktop Edition customers wait several months and have to pay for a new version like SSR 2014 Desktop Edition? I need to know what is being done by the software developers. If I have to wait several months then I guess I'll have to shop around for new system image backup/restore software like Acronis True Image. I've been using Symantec system image software for years so I'd prefer to not have to start using another company's product.
SSR 2013 to External Drive - Drive is Disappearing
I have a large installed base of laptops and desktops, all with an external Western Digital 1TB USBdrive. I run SSR daily to send an image to the external drive as the backup destination. However, frequently a handful of machines - not a consistent set - will no longer "see" the drive. When viewing the SSR console, the backup destination shows "Not Available". The computer itself still can see and access the drive. If I disconnect and reconnect the drive, SSR will see it again and the task can run successfully. Then some time later (days, weeks, months) the drive will disappear again. There is no consistency to this error - all software is at the same version, all external drives are the same, all laptops and desktops are identical, all patches are managed through SCCM so all Windows patches are at the same version, and yetit's always different machines that come up with this issue. Anyone else out there experiencing this or perhaps have a suggested fix? (Besides finding a different disaster recover solution - which is definitely on the table at this point!) Thanks!