Windows 2003 unsupported BusLogic SCSI adapter

Similar Questions

• Imported the Parallels VM, now I get "BusLogic SCSI adapter is not supported for 64-bit customers."

  I have a virtual machine 64-bit Fedora 16 that I use in Parallels Desktop.  During my first installation of VMWare Fusion 5, I had the opportunity to import this VM.  I did that, but when I boot, the virtual machine is suspended.  I went to the configuration of the virtual machine in VMWare and fixed a few things than the failed import.  Now I when I start the VM, I get this dialog box:

  The BusLogic SCSI adapter is not supported for 64-bit guests.

  I searched on the web and this forum, and I can't find information on solving this problem.

  I do not necessarily first as suggested by the other answer on this subject and instead, add the following line to the configuration of the Virtual Machine's .vmx file.

  scsi0.virtualDev = "lsilogic"
  

  This should fix the error message that you get without having to directly edit the hard.  Take a look at: changing the file .vmx for your VM from VMware Fusion (1014782)  

  That said, if you want detailed according to the existing real configuration recommendations then... To help understand what components are, how best to provide comprehensive diagnostic information is to use the command "Collect information to Support" the Fusion of VMware (menu bar) > help > collect Support information and then attach the .tgz file it created on your desktop for a response post.

• The BusLogic SCSI adapter installation

  I'm running Windows XP (32-bit) with VMWare Fusion 4.1.1 on an iMac Intel Core i7, and I get a warning message of: Windows XP includes not the drivers for the card SCSI BusLogic VMware Fusion using virtual SCSI devices.

  (1) I found and downloaded vmscsi - 1.2.0.4, added a virtual disk (changed the boot order to boot from the hard drive and not the floppy drive).

  (2) booted up my VM

  Went 3) in Device Manager and only see VMware SCSI Controller.

  4) updated with the vmscsi - 1.2.0.4. pilot

  (5) stop and start the virtual machine, and he always complains about not having driver.

  I searched on the VMware site and found that someone suggested to use another SCSI driver, so I download - vmscsi - lsi.flp

  (1) swapped out with the new SCSI driver diskette

  (2) booted up my VM

  (3) went into the Device Manager and set to update from VMware SCSI controller with the new driver (vmscsi-lsi)

  (4) stop, start the virtual machine, and he always complains.

  (5) it turns out that those who is drivers Dell.

  Reinstalled the VMware tools on this VM, stop and start my VM. He always complains about not having the SCSI drivers.

  Help!

  I tried to add a new hardware device, but that no longer works.

  How to solve this problem? (I got my VM lock for 10 minutes at a time, while I'm either stuff copy a CD in the C: or when I click on Explorer, so I really hope that driver problems will solve the lock of the questions, which give rise to "Explorer (not responding)"

  Thank you!

  Hi Jeff,

  Errors in your vmware.log suggest that the host CD/DVD drive runs badly trying to read data from the disk.  Are you sure that the drive itself is OK?  (I guess it's a CD/DVD drive internal regular... without the upper part of the vmware.log, I can't say what it is or how it is connected.)

  I'm not 100% sure, but my guess is that tools errors are caused by the virtual machine stuck while trying to read the CD/DVD, and that the problem of CD/DVD will these messages to disappear for the most part.  Although I don't understand yet why the virtual machine would be so totally stuck because of problems with CD/DVD...

  If you have enough available disk space on your iMac, can you try to use the host Applications > utilities > disk utility to create an image file in the media CD/DVD and then fix the resulting image in .cdr to the virtual CD/DVD drive in Fusion?  I suggest this as a step diagnostic (to say if the problem is with the disc, Fusion, or both), and not as a long term solution.

  Thank you

  --

  Darius

• Erroneous Buslogic SCSI driver WARNING - WinXP running in Fusion on Mac

  En Fusion 4 and now in Fusion 5, whenever I start my Windows XP VM I get this warning: "Windows XP does not include drivers for the BusLogic SCSI adapter used for SCSI devices virtual VMware Fusion." To use these virtual SCSI devices, install the VMware driver in the virtual machine. «Download the driver of "http://vmware.com/info?id=43".»  However, the virtual machine works very well.  I would like to get rid of this false alarm, and I searched the threads on this forum but also by looking at Knowledge Base articles.  I find information about it and even get instructions on adding a line (buslogic.nodriver = 'FALSE') to a configuration file to disable the warning, but the suggestions do not work or there is no location where the configuration file is supposed to be.  I'm under Fusion on a MacBook Pro OS X 10.8.2 retina.

  Does anyone have a method to update on how to stop this annoying warning?

  Thank you

  Scott

  Hi Scott,.

  The procedure has not changed, there is no update instructions.

  You can add the option directly in the virtual computer configuration file by following the instructions in the Knowledge Base article.

  I note that your message said that you added

  RiverdBusLogic.no = "FALSE".

  but the option is case sensitive and must be entered as well

  River BusLogic.noD= "FALSE".

  I don't know if it's a typo in your post on the forum here or if that's what you used in your virtual machine configuration.  If you used the name of lower-box only in your previous attempts, maybe try again with a capital "D" and see if that fixes the problem.

  See you soon,.

  --

  Darius

• How do I change the logic LSI Logic SCSI's BUS controller in a prompt Windows 2003 running on ESX 3.5 U4

  I'm unable to find clear instructions on how to change the logic LSI Logic SCSI's BUS controller in a Windows 2003 running on ESX 3.5 U4 prompt.

  If someone could help me I really appreciate.

  Thank you

  Cannot not just off VM, go to the settings on the Hardware tab, Type of SCSI controller, click on modify the type and change of LSI Logic.

• Adding a SCSI drive to Windows 2003 Web Server

  Can someone provide me with a diagram to install additional hard disks in a VM Ware Workstation using Windows 2003 Web Server.

  I use the demo version of Workstation 6.5. I would like to add to the readers of more the C:"" drive.

  So far, I created using the VM & gt; Setting & gt; Material & gt; Add.

  Instructions explain to use partitioning and formattting tools in the operating system

  When I go to computer management & gt; Device Manager the two additional disk as VMware, VMware Virtual SCSI disk

  It seems that they are already formatted. The drive letter for them do not appear in my computer. Where is the tool for partitioning and formatting?

  How can I go to the system BIOS/CMOS settings to see newly created the associated drive letter and the virual drive configurations?

  Click in the console and F2 on boot or bios.forceSetupOnce = "TRUE" can be inserted into a VMX file.

  Kind regards

  EvilOne

  NOTE: If your question or problem has been resolved, please mark this thread as answered and awarded points accordingly.

• Windows 2003 Server R2 on vmware Server 2

  Hello

  I tried to install Windows 2003 Server R2 on vmware Server 2 using SCSI drives and the driver aviailable at vmware.com. Despite the dirver is responsible (FDD, F6 at startup, image etc.) the Setup program does not detect the disc.

  Can help?

  TIA

  Matthias

  Hello.

  You use the LSI or BusLogic adapter in your virtual machine?

• From ESX 3.5 to Windows 2003 VM Workstation 10

  I copied a windows 2003 vm from esx 3.5 and want to run under 10 workstation.

  The problems seem to be: 1. He starts but not the mouse, etc. 2. try to restart and it will not stop. 3. try to upgrade of the tools, and it does not restart. 4 get error on buslogic scsi problem

  5. If the power off, then NTLDR is missing when restart it.

  Would appreciate some advice on how best to move the windows 2003 VM from ESX 3.5 to 10 Workstation

  Regards, Mark

  Hello and welcome to the communities.

  How did you move it, or what was the process? You might want to try VMware Converter, if you do not.

• VMware Paravirtual SCSI adapter

  Is there a reason the "VMware Paravirtual SCSI" is not to use it?

  I would use this adapter for each VM of data partitions (not partitions to boot).

  Reason: Have the hole identitical environment.

  I have only heard one drawback: VMs with e/s low will have no gain performance on the SCSI adapter which is usually used.

  Thanks for your review!

  Simon

  Is there a reason the "VMware Paravirtual SCSI" is not to use it?

  If you do not need FT, I see no reason right now.

  See http://blog.scottlowe.org/2009/07/05/another-reason-not-to-use-pvscsi-or-vmxnet3/

  I would use this adapter for each VM of data partitions (not partitions to boot).

  I guess you know that, anyway.

  of the http://www.vmware.com/support/vsphere4/doc/vsp_esx40_u1_rel_notes.html

  Improved VMware's paravirtualized SCSI support

  Support for devices connected to an adapter (PVSCSI) paravirtualized SCSI boot drive has been added for Windows 2003 and 2008 guest operating systems...

  André

• Installing a SCSi adapter

  Hello

  I've got installed ESXi on our Dell Poweredge server, we have a Windows 2003 virtual server and we are trying to install a new card "Adaptec" SCSi 2940 UltraWide. The server is picked up that we can access the etc bio card, but how can I add it to our virtual server? I tried connecting to the server and check the Device Manager, but there is no new material. I also tried click with the right button on the server and check in the management options in the VMWARE management console. They say there is no device SCSi to the choice is available.

  Nothing is connected to the SCSi controller for the moment.

  As I write until you cannot virtualize the adapter but only connected devices.

  André

  * If you found this device or any other answer useful please consider awarding points for correct or helpful answers

• Upgrade of Windows 2003 to 2012 r2 DC replication problem

  Hello

  I added R2 2012 Windows server to windows 2003 sp2 (primary DC) DC and promotes as DC. After the promotion, I run dcdiag and it shows errors.

  Each of the servers have three NICs connected to different networks.

  Please help me with your expertise since I have to raise this Monday.

  Thank you

  Kind regards

  Charaf-eddine

  Here the dcdiag output new DC

  Directory Server diagnosis

  Perform the initial configuration:

  Trying to find the server at home...

  Home Server = CADPDC1

  * Identified AD forest.
  Made the initial collection of information.

  Make the required initial tests

  Test server: Default-First-Site-Name\CADPDC1

  Commencement of the trial: connectivity

  CADPDC1.engineer.com host name resolution error by

  IPv6 stack.

  WARNING: could not confirm the identity of this server in the

  Directory and names returned by DNS servers. Host name

  fixed error 0x2af9 "host is known."

  ......................... CADPDC1 passed test connectivity

  Primary testing

  Test server: Default-First-Site-Name\CADPDC1

  Commencement of the trial: advertising

  WARNING: DsGetDcName returned information for

  \\cadpdc. Engineer.com, when we tried to reach CADPDC1.

  SERVER IS NO ANSWER or IS NOT considered AS APPROPRIATE.

  ......................... CADPDC1 was not able to test advertising

  Beginning of the test: FrsEvent

  There are warning or error events in the last 24 hours after the

  SYSVOL is shared.  Don't not SYSVOL replication problems can cause

  The Group of political problems.
  ......................... CADPDC1 test FrsEvent

  Commencement of the trial: DFSREvent

  ......................... CADPDC1 test DFSREvent

  Commencement of the trial: SysVolCheck

  ......................... CADPDC1 test SysVolCheck

  Beginning of the test: KccEvent

  ......................... CADPDC1 test KccEvent

  Beginning of the test: KnowsOfRoleHolders

  [CADPDC] DsBindWithSpnEx() failed with the error-2146893022,

  The name main target is incorrect...
  ATTENTION: CADPDC is the owner of the schema, but does not meet the DS RPC

  Bind.

  [CADPDC] LDAP bind failed with error 8341,

  A directory service error has occurred...
  ATTENTION: CADPDC is the owner of the schema, but does not respond to LDAP

  Bind.

  ATTENTION: CADPDC is the owner of the domain, but does not meet the DS RPC

  Bind.

  ATTENTION: CADPDC is the owner of the domain, but does not respond to LDAP

  Bind.

  ATTENTION: CADPDC is the owner of PDC, but does not meet the DS RPC

  Bind.

  ATTENTION: CADPDC is the owner of PDC, but does not respond to the LDAP bind.

  ATTENTION: CADPDC is the owner of RID, but does not meet the DS RPC

  Bind.

  ATTENTION: CADPDC is the owner of RID, but does not respond to the LDAP bind.

  ATTENTION: CADPDC is the owner of Infrastructure Update, but is not

  meet DS RPC Bind.

  ATTENTION: CADPDC is the owner of Infrastructure Update, but is not

  respond to LDAP Bind.

  ......................... CADPDC1 failed test KnowsOfRoleHolders

  Beginning of the test: MachineAccount

  ......................... CADPDC1 test MachineAccount

  Beginning of the test: NCSecDesc

  ......................... CADPDC1 passed test NCSecDesc

  Beginning of the test: NetLogons

  Cannot connect in the NETLOGON share. (\\CADPDC1\netlogon)

  [CADPDC1] An net use or LsaPolicy operation failed with error 67.

  The network name was not found...

  ......................... CADPDC1 failed test NetLogons

  Commencement of the trial: ObjectsReplicated

  ......................... CADPDC1 test ObjectsReplicated

  From test: Replications

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: DC = ForestDnsZones, DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:21.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: DC = DomainDnsZones, DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:21.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: CN = Schema, CN = Configuration, DC = engineering, DC = com

  The replication generated an error (1727):

  The remote procedure call failed and did not execute.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:06.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: CN = Configuration, DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:07.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:21.

  1 failures have occurred since the last success.

  ......................... CADPDC1 failure test replications

  Beginning of the test: RidManager

  ......................... CADPDC1 failed test RidManager

  Commencement of the trial: Services

  ......................... CADPDC1 test passed Services

  Beginning of the test: SystemLog

  A warning event occurred.  Event ID: 0x000727A5

  Generated time: 27/06/2014-17:01:38

  The event string:

  The WinRM service is not listening to the WS-Management requests.

  A warning event occurred.  Event ID: 0 x 80050004

  Generated time: 27/06/2014-17:05:03

  The event string:

  HP 1 GB 2 332T adapter ports Ethernet: the network link is down.  Check that the network cable is connected correctly.

  A warning event occurred.  Event ID: 0xA004001B

  Generated time: 27/06/2014-17:05:06

  The event string: HP NC112T PCIe Gigabit Server Adapter

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:39

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was LDAP/cadpdc.engineer.com/*** Email address is removed from the privacy *. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:39

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was ldap/cadpdc.engineer.com/*** address email is removed from the privacy *. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:41

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was of cadpdc$. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:43

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was GC/cadpdc.engineer.com/engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  A warning event occurred.  Event ID: 0x000727AA

  Generated time: 27/06/2014-17:05:43

  The event string:

  The WinRM service could not create the following SPNS: WSMAN/CADPDC1.engineer.com; WSMAN/CADPDC1.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:55

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was cifs/cadpdc.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  A warning event occurred.  Event ID: 0 x 84350444

  Generated time: 27/06/2014-17:05:58

  The event string:

  Information System Officer: health: Post errors have been detected.  One or more errors of Power-On-Self-Test were detected when the server starts.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:59

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was E3514235-4B06-11D1-AB04-00C04FC2DCD2/5122bd13-c8ac-4265-a879-3a6831224994/*** Email address is removed from the privacy *. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:59

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was ldap/cadpdc.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0x0000410B

  Generated time: 27/06/2014-17:05:59

  The event string:

  The request for a new account identifier pool failed. The operation will be retried until the request succeeds. The error is

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:06:07

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was LDAP/cadpdc.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 27/06/2014-17:06:30

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0x0000041D

  Generated time: 2014/06/27 17:07:07

  The event string:

  The processing of Group Policy failed. Windows could not resolve the user name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 2014/06/27 17:11:32

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 27/06/2014-17:16:33

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:16:38

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was LDAP/5122bd13-c8ac-4265-a879-3a6831224994._msdcs.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 2014/06/27 17:21:35

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  ......................... CADPDC1 failed test SystemLog

  Commencement of the trial: VerifyReferences

  ......................... CADPDC1 test VerifyReferences

  Running partition tests: ForestDnsZones

  Beginning of the test: CheckSDRefDom

  ......................... ForestDnsZones passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... ForestDnsZones passed test

  CrossRefValidation

  Running partition tests: DomainDnsZones

  Beginning of the test: CheckSDRefDom

  ......................... DomainDnsZones passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... DomainDnsZones passed test

  CrossRefValidation

  Running partition tests: schema

  Beginning of the test: CheckSDRefDom

  ......................... Schema passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... Schema passed test CrossRefValidation

  Running partition tests: Configuration

  Beginning of the test: CheckSDRefDom

  ......................... Configuration test past CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... Configuration test past CrossRefValidation

  Running partition tests: engineer

  Beginning of the test: CheckSDRefDom

  ... engineer passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ... engineer passed test CrossRefValidation

  Running tests of the company: engineer.com

  Commencement of the trial: LocatorCheck

  ... engineer.com passed test LocatorCheck

  Commencement of the trial: cross-site

  ... engineer.com passed test intersite

  Hi Chamarasi,

  I suggest that you post the application on Microsoft TechNet forum because we have experts working on these issues. You can check the link to post the same query on TechNet:

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  Please do not hesitate to contact us if you have other questions related to Windows.

• problem with vpnclient 64 bit for windows 2003 //442:failed to activate the virtual card.

  Hello

  I need to know is below customer vpn will work for windows 2003 64-bit, according to the release notes I doubt it will work.

  name of the file - vpnclient-winx64-msi - 5.0.07.0290 - k9.exe

  release notes - http://www.cisco.com/en/US/docs/security/vpn_client/cisco_vpn_client/vpn_client5007/release/notes/vpnclient5007.html#wp63537

  WILL take the ip address but does not connect. It is possible some configuration or ASA image issue that her first time, we try to use 64-bit OS, for 32 bit OS vpn client works very well.

  on the pc screen, it says - reason-442: impossible to activate the virtual card.

  Here are the logs of vpn clinet when I tried to connect ASA5520. Version 7.0 (8).

  Cisco Systems VPN Client 5.0.07.0290 Version
  Copyright (C) 1998-2010 Cisco Systems, Inc.. All rights reserved.
  Customer type: Windows, Windows NT
  Running: 5.2.3790 Service Pack2
  Config files directory: C:\Program Files (x 86) \Cisco Systems\VPN Client\

  1 15:38:03.921 27/01/11 Sev = Info/4 CM / 0 x 63100002

  Start the login process

  2 15:38:03.937 27/01/11 Sev = Info/4 CM / 0 x 63100004

  Establish a secure connection

  3 15:38:03.937 27/01/11 Sev = Info/4 CM / 0 x 63100024

  Attempt to connect with the server "203.199.30.190".

  4 15:38:04.125 27/01/11 Sev = Info/4 CM/0x6310000E

  ITS established Phase 1.  1 crypto IKE Active SA, 0 IKE SA authenticated user in the system

  5 15:38:04.140 27/01/11 Sev = Info/4 CM / 0 x 63100015

  Launch application xAuth

  6 15:38:09.515 27/01/11 Sev = Info/4 CM / 0 x 63100017

  xAuth application returned

  7 15:38:09.515 27/01/11 Sev = Info/4 CM/0x6310000E

  ITS established Phase 1.  1 crypto IKE Active SA, 1 IKE SA authenticated user in the system

  8 15:38:10.562 27/01/11 Sev = Info/4 CM / 0 x 63100019

  Data in mode Config received

  9 15:38:10.781 27/01/11 Sev = WARNING/2 CVPND/0xE340002C

  Impossible to activate the 64-bit GOES after timeout

  10 15:38:10.781 27/01/11 Sev = WARNING/3 CVPND/0xE3400029

  The Client was unable to activate the virtual card on 64-bit Windows

  11 15:38:10.781 27/01/11 Sev = WARNING/2 CM/0xE310000A

  Impossible to activate the virtual map

  12 15:38:10.781 27/01/11 Sev = Info/6 CM/0x6310003A

  Cannot restore the file road changes.

  13 15:38:10.781 27/01/11 Sev = Info/6 CM / 0 x 63100037

  The routing table was returned to the original state before the virtual card

  14 15:38:10.859 27/01/11 Sev = Info/4 CM / 0 x 63100035

  The virtual adapter has been disabled

  15 15:38:10.859 27/01/11 Sev = WARNING/2 IKE/0xE300009B

  Has no active IPSec security association: impossible to activate the virtual card (NavigatorQM:936)

  16 15:38:10.859 27/01/11 Sev = WARNING/2 IKE/0xE30000A7

  SW unexpected error during the processing of negotiator fast Mode:(Navigator:2263)

  17 15:38:11.546 27/01/11 Sev = Info/4 CM / 0 x 63100012

  ITS phase 1 deleted before first Phase 2 SA is caused by 'unknown '.  Crypto 0 Active IKE SA, 0 IKE SA authenticated user in the system

  18 15:38:11.546 27/01/11 Sev = Info/5 CM / 0 x 63100025

  Initializing CVPNDrv

  19 15:38:11.578 27/01/11 Sev = Info/6 CM / 0 x 63100046

  Set indicator established tunnel to register to 0.

  20 15:38:40.953 27/01/11 Sev = Info/4 CM / 0 x 63100002

  Start the login process

  21 15:38:40.953 27/01/11 Sev = WARNING/2 CVPND/0xA3400019

  Fixing error socket:-21. (DRVIFACE:1234)

  22 15:38:40.968 27/01/11 Sev = Info/4 CM / 0 x 63100004

  Establish a secure connection

  23 15:38:40.968 27/01/11 Sev = Info/4 CM / 0 x 63100024

  Attempt to connect with the server "203.199.30.190".

  24 15:38:41.156 27/01/11 Sev = Info/4 CM/0x6310000E

  ITS established Phase 1.  1 crypto IKE Active SA, 0 IKE SA authenticated user in the system

  25 15:38:41.171 27/01/11 Sev = Info/4 CM / 0 x 63100015

  Launch application xAuth

  26 15:39:08.031 27/01/11 Sev = Info/4 CM / 0 x 63100017

  xAuth application returned

  27 15:39:08.046 27/01/11 Sev = Info/4 CM/0x6310000E

  ITS established Phase 1.  1 crypto IKE Active SA, 1 IKE SA authenticated user in the system

  28 15:39:09.093 27/01/11 Sev = Info/4 CM / 0 x 63100019

  Data in mode Config received

  29 15:39:09.312 27/01/11 Sev = WARNING/2 CVPND/0xE340002C

  Impossible to disable the AV 64-bit after timeout

  30 15:39:09.312 27/01/11 Sev = WARNING/3 CVPND/0xE340002A

  The customer does not have to disable the virtual card on 64-bit Windows

  31 15:39:19.937 27/01/11 Sev = WARNING/3 CVPND/0xA340000D

  The virtual card did not recognize the operating system.

  32 15:39:19.937 27/01/11 Sev = WARNING/2 CM/0xE310000A

  Impossible to activate the virtual map

  33 15:39:19.937 27/01/11 Sev = Info/6 CM/0x6310003A

  Cannot restore the file road changes.

  34 15:39:19.937 27/01/11 Sev = Info/6 CM / 0 x 63100037

  The routing table was returned to the original state before the virtual card

  35 15:39:20.109 27/01/11 Sev = WARNING/2 CVPND/0xE340002C

  Impossible to disable the AV 64-bit after timeout

  36 15:39:20.109 27/01/11 Sev = WARNING/3 CVPND/0xE340002A

  The customer does not have to disable the virtual card on 64-bit Windows

  37 15:39:20.281 27/01/11 Sev = WARNING/2 CVPND/0xE340002C

  Impossible to disable the AV 64-bit after timeout

  38 15:39:20.281 27/01/11 Sev = WARNING/3 CVPND/0xE340002A

  The customer does not have to disable the virtual card on 64-bit Windows

  39 15:39:20.578 27/01/11 Sev = WARNING/2 CVPND/0xE340002C

  Impossible to disable the AV 64-bit after timeout

  40 15:39:20.578 27/01/11 Sev = WARNING/3 CVPND/0xE340002A

  The customer does not have to disable the virtual card on 64-bit Windows

  41 15:39:20.953 27/01/11 Sev = WARNING/2 CVPND/0xE340002C

  Impossible to disable the AV 64-bit after timeout

  42 15:39:20.953 27/01/11 Sev = WARNING/3 CVPND/0xE340002A

  The customer does not have to disable the virtual card on 64-bit Windows

  43 15:39:21.437 27/01/11 Sev = Info/4 CM / 0 x 63100035

  The virtual adapter has been disabled

  44 15:39:21.437 27/01/11 Sev = WARNING/2 IKE/0xE300009B

  Has no active IPSec security association: impossible to activate the virtual card (NavigatorQM:936)

  45 15:39:21.437 27/01/11 Sev = WARNING/2 IKE/0xE30000A7

  SW unexpected error during the processing of negotiator fast Mode:(Navigator:2263)

  46 15:39:22.046 27/01/11 Sev = Info/4 CM / 0 x 63100012

  ITS phase 1 deleted before first Phase 2 SA is caused by 'unknown '.  Crypto 0 Active IKE SA, 0 IKE SA authenticated user in the system

  47 15:39:22.046 01/27/11 Sev = Info/5 CM / 0 x 63100025

  Initializing CVPNDrv

  48 15:39:22.062 27/01/11 Sev = Info/6 CM / 0 x 63100046

  Set indicator established tunnel to register to 0.

  Also you need to be in 8.0 code run client Anyconnect.

  --

  Robet

• Newly converted Virtual Machine Windows 2003 contains no hard drive

  I'm looking on the advice of this problem.

  I used vConverter 4.0 to transform the four physical servers to virtual machines.  Two of my attempts ended in failure.  One was a standard Server Windows 2000 running as a web server. He just cut to 3% or 4%. Let this old trash server at the moment.

  The second is a Windows 2003 Web Edition Server.  The P2V process actually all the way!   But I can't start. I discovered that the physical server C drive was not there?  When you change the properties I see only one hard drive (it would have taken to 10 GB and 20 GB) it seemed to me that if the configuration in the setup of P2V has been misinterpreted?...

  Initially, I made it clear that the 51 GB drive C and 74 GB - D drive should become a 10 (only use 4.8) and a 20 GB (only 11.5 GB used).  Instead, I found myself with a huge 72GO disk in the virtual machine

  In this fourth attempt, trying now not to tamper with disk sizes and rely solely on provisioning.  And there is room for the 51 + 74 GB of disks on the ESXi host expected they exploit the full potential.

  But it really intrigues me I get a different result that I opted for in the configuration of the P2V.

  No explanation?

  The server in question is from the disks IDE and a legacy mainboard with an old Pentium 4 processor - not really a server.  On the other hand I have converted two physical successfully servers, just until I came across this problem. It was 12 to 14 years old Compaq DL380 G1 servers with SCSI disks.

  I think part of the problem is that you cannot change the type of IDE SCSI controller (it's in step 3). You can try the following steps, but if it was me I would just start the conversion, resizing disks you want and ensure are using a SCSI controller

  http://KB.VMware.com/kb/1016828

• How VM Windows 2003 can I make it work with the following equipment

  Hi guys,.

  Suppose that I buy the server below. How VM Windows 2003 I can ru without performance issues. With resource allocation obv.

  PowerEdge R610 Rack chassis for up to 6 x 2.5 "hard drives

  |

  Catalogusnummer:	SV4R610REL 282823
  Module	Tricky	ProductCode (verbergen).	SKU (verbergen).	ID (verbergen).
  Base	PowerEdge R610 Rack chassis for up to 6 x 2.5 "hard drives	205064		1
  Additional processor	No additional processor	205078		2
  Geheugen	32 GB memory for 2 CPUs, DDR3 1066 MHz (8X4Go RDIMMS)	205192		3
  Economic stations	16 X DVD +/-RW SATA Drive ROM	205109		16
  Shipping documents	R610 shipping Documents EMEA1 (English/French/German/Spanish/Russian/Hebrew)	205065		21
  Basic warranty	1 jaar basisgarantie - next business day	206049		29
  Ondersteuningsdiensten	Basic 3 year - next business day warranty	206123		30
  Installation services	You have chosen not to take the Dell PowerEdge installation service	76588		32
  Systeembeheer	DVD of the System Documentation and Dell OpenManage electronic for PowerEdge R610	205116

  49

  Rackmontage voor rails

  Not included the racks

  11433

  88

  Order information

  PowerEdge order - Belgium

  32377

  111

  Processor

  Intel® Xeon® E5540, 2.53 Ghz Cache 8 MB, 5.86 GT/s QPI, Turbo, HT, 1066 MHz Max Memory

  205495

  146

  Power cable

  Power cord, PDU (Rack)

  5605

  207

  2nd hard drive

  (4) 300 GB, SAS, 2. 5 - inch, 10 K rpm additional hard drive (Hot Plug)

  205590

  217

  1 RAID - SCSI-controllerkaart

  6iR SAS internal RAID controller card

  212046

  278

  In of fabriek voorgeïnstalleerd besturingssysteem

  Not included

  8007

  285

  OMLIJSTING vooraan

  R610 Rack bezel

  205115

  669

  RAID-connectiviteit

  CFI: RAID 5 + spare. Min 4 HDD

  274642

  1009

  As

  Power output high, not redundant (1 power supply), 717W, BIOS Performance parameter

  205113

  1015

  1 hard drive

  300 GB, SAS, 2. 5 inch, 10 K RPM Hard Drive (Hot Plug)

  205569

  1209

  TCP/IP Offload Engine Enablement

  Ethernet embedded Broadcom Gigabit LOM with TOE 4 p

  77384

  1310

  Serverbeheerkaarten

  iDRAC6 Express Server Management Card

  205619

  1314

  > Why should I the extra CPU?

  UH... because you ask how much Windows 2003 virtual machine, you can run... I GUESS that means more out... That more CPU more the better overall performance of ESX, VM and ESX operating system are designed to work on ALL hearts, so the more hearts of better performance.

  In your config version right now, I wouldn't go above 20 VM.  as you plan to use only 1 hard drive?

  If you use 1 disc, you realize that you have only 1 disc do all the work... right?

• Windows 2003 fails to start after the conversion from a virtual hard disk with vSphere Standalone Converter 4.0.1

  Hello

  I've recently updated my host to vSphere 4. I've also upgraded to vSphere Converter 4.0.1. However, when I convert a Microsoft Windows 2003 virtual hard drive in vSphere, the resulting virtual machine does not start. He gets just after the BIOS screen, then turns black with only a white line in the upper left corner of the console.

  I tried the hot and cold conversions. I tried changing the different settings of default conversion. I tried to remove the source machine and recreate.

  It worked well under ESX3.5, so I wonder what I'm doing wrong on vSphere.

  Any help appreciated.

  Thank you.

  In v4 disk are in SCSI format only.

  Probably also the source was in the SCSI format... so v7 to the IDE format give you not configured in the bootloader of the disks.

  André