Hi,

SEP_Inst log can tell more details.

Please attach SEP_Inst log file which would be under %temp% file

Also check drives are not mapped .

Hi,

Any update on this

This may help. When installing the other drive(s) in your Windows 7 system, the OS offers you to set it up with a drive letter or to attach it in a directory, always give it a drive letter. 

Seeing the same error the install does not seem to generate a log. No mapped drives on system documenypts and settings directory is a junction point pointing at other physical drive on system. System is XP pro SP3. Any direction at all would be an help. Have tried interactive install also.

Here is an update with the relevant lines from the log file

further info: The device is a notebook that has a SSD (C) and a SATA (D) and is provisioned on Win7 so that ProgramData and Users are located on the SATA drive but with links from the C drive

I guess this is what the system means by Reparse Points (the links)

If this is not allowed than:

- this should be mentioned in some documentation (i could not find it anywhere)

- workaround to install at a custom location needs to be given

This is incredibly frustrating.

The customer I've upgraded to SEP12 SBE was an early adopter of SEP11 and boy did he pay for it, the network app blocking issue on an early MR caused his business function to be down until we could install the newest MR. Then that MR filled his server's C drive with multiple copies of the temporary virusdefs and the server started to crash due to lack of disk space. (it took hours to remove the 30+ gb of tmp*.tmp files) To avoid that problem in the future we created some junction points for a few symantec folders on the C drive to ensure this never happened again.

With the new SEP12 I ran cleanwipe to make sure the old version was completely gone and then made sure those same common folders were still junction pointed to the data drive.

I installed SEPM to D: but alas it still spent a gig or two dropping things into the C drive.

Ironically, now the server's AV protection won't install because of the reparse points we created because of the errors with the previous version.

Luckily this is the only customer that stuck with Symantec after the SEP11 debacle every other customer is happily using AV that requires no tweaking.

I'd be really happy if they fixed this or allowed installing to anything other than the C drive.