Quantcast
Channel: Symantec Connect - Backup and Recovery - Known Issues
Viewing all articles
Browse latest Browse all 178

Symantec System Recovery Physical to virtual (P2V) conversion of Windows 2003 Standard Sp2 x86 to a Hyper-V results in guests failing to detect NIC and start integration services.

$
0
0
Severity: 
Minor functionality
Status: 
Investigating/gathering information
Tech Note: 
197974
Problem

When attempting to convert a system image file using the Symantec System Recovery Physical to virtual (P2V) conversion utility, systems running Microsoft® Windows Server® 2008 Standard Version 6.0.6002 Service Pack 2 32-bit to a Hyper-V guest system results in a guest system that fails to detect its network card, integration services fail to start, and the Hyper-v Manager does not report the guest's heartbeat. This does not appear to occur using other 3rd party converting utilities for this system as well as using the Symantec System Recovery Physical to virtual (P2V) conversion utility on images created from different Windows operating systems.

 
Error

On some virtual guests, upon initial boot, the following error had occurred:

"virtual adapter not found"
 
Environment
  • Microsoft® Windows Server® 2008 Standard Version 6.0.6002 Service Pack 2 32-bit
  • Hyper-V host running on a Microsoft® Windows Server® 2008 R2 Sp1 system
  • Backup Exec System Recovery 2010 -or- Symantec System Recovery 2011

 

 
Cause

Issue is under investigation

 
Solution

(Workaround) - Manually enable the, 'Detect Hal,' check box within the System Configuration utility:

  1. Go to START | RUN.
  2. Type MSCONFIG and press enter.
  3. Click on the BOOT tab and press enter.
  4. Click the ADVANCE OPTIONS button.
  5. Check the DETECT HAL check box.
  6. Click the Apply button.
  7. Click the OK button
  8. Click the Restart Now button

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
 
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see  http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
 

NOTE:
Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.

 


Viewing all articles
Browse latest Browse all 178

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>