Migration on windows server 2003 to 2012 r2 by using IIS 6.0 what are parameters are changed means supported and non suported parameters and configurations?

In my project am going to migrate windows server 2003 to 2012 r2 by using IIS 6.0? what are the parameters are changed and what are the parameters are not supported and what are the modules need to change?
Please give the related answer as soon as posssibule. that is more help for me?
Thanks,
vamsikrishna.

1. This seems to be incomplete description.
2. You can enable legacy technologies while installing roles and features.
3. For application pool(s) you should consult respective developer/vendor team(s) for help.
Regards
Milos

Similar Messages

ADPrep Migration from Windows Server 2003 to 2012 Foundation Server fails with error 0x80004005

Hi all,
Having a problem the forums and Google have been unsuccessful in helping me with. Server is Windows 2003 R2, migrating to Windows Server 2012 foundation. Have tried the AD Migration on the new 2012 Foundation server both as a standalone server
and a domain server member before running the migration. I get the following error:
ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning
I've checked the ADprep logs and have found the following:
[2013/01/22:11:15:01.000]
Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[2013/01/22:11:15:01.001]
LDAP API ldap_search_s() finished, return code is 0x0
[2013/01/22:11:15:01.001]
Adprep checked to verify whether operation cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local has completed.
[Status/Consequence]
The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
[2013/01/22:11:15:01.001]
Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[2013/01/22:11:15:01.001]
LDAP API ldap_search_s() finished, return code is 0x20
[2013/01/22:11:15:01.001]
Adprep verified the state of operation cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
[Status/Consequence]
The operation has not run or is not currently running. It will be run next.
[2013/01/22:11:15:01.021]
Adprep was unable to complete because the call back function failed.
[Status/Consequence]
Error message: Unable to access the computer "SERVER.apl.local". The network path was not found.
(0x80070035).
[User Action]
Check the log file ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
DSID Info:
DSID: 0x1811132a
winerror = 0x1f
NT BUILD: 9200
NT BUILD: 16384
[2013/01/22:11:15:01.021]
Adprep was unable to update forest information.
[Status/Consequence]
Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.
[User Action]
Check the log file, ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
We did have AVAST Antivirus installed on the server but this was removed. Any idea's?
Jason.
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

Hi Biswajit et. al., thanks for your help thus far, it is greatly appreciated...
Unfortunately I had already disabled the NIC's on both hosts. They currently remain disabled. I've just tried turning off IPv6 as well and no luck.
PortQry came back fine (I think) :)
=============================================
Starting portqry.exe -n server.apl.local -e 135 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 135 (epmap service): LISTENING
Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[dhcpcsvc]
UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
ncalrpc:[LRPC00001d40.00000001]
UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
ncalrpc:[LRPC00001448.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[OLE4EF57D32A0DB45F9A64653468D7C]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000012ac.00000001]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncacn_np:\\\\SERVER[\\pipe\\tapsrv]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[tapsrvlpc]
UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
ncalrpc:[unimdmsvc]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncalrpc:[W32TIME_ALT]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:\\\\SERVER[\\PIPE\\W32TIME_ALT]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncacn_ip_tcp:10.0.0.3[1111]
UUID: 6bffd098-a112-3610-9833-46c3f874532d
ncalrpc:[DHCPSERVERLPC]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncacn_ip_tcp:10.0.0.3[1111]
UUID: 5b821720-f63b-11d0-aad2-00c04fc324db
ncalrpc:[DHCPSERVERLPC]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncalrpc:[LRPC00000480.00000001]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncalrpc:[LRPC00000480.00000001]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncalrpc:[LRPC00000480.00000001]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
UUID: 493c451c-155c-11d3-a314-00c04fb16103
ncacn_ip_tcp:10.0.0.3[1092]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_ip_tcp:10.0.0.3[1090]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncalrpc:[LRPC00001060.00000001]
UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_ip_tcp:10.0.0.3[1090]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncalrpc:[LRPC00001060.00000001]
UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:10.0.0.3[1067]
UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC00000d10.00000001]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:10.0.0.3[1067]
UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC00000d10.00000001]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:10.0.0.3[1067]
UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC00000d10.00000001]
UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:10.0.0.3[1048]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000004d4.00000001]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:10.0.0.3[1032]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[audit]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[securityevent]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[protected_storage]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[dsrole]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:10.0.0.3[1026]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[NTDS_LPC]
UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:10.0.0.3[1027]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[audit]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[securityevent]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ab
ncacn_http:10.0.0.3[1027]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[audit]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[securityevent]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[dsrole]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncalrpc:[NTDS_LPC]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_http:10.0.0.3[1027]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[audit]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[securityevent]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[protected_storage]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[dsrole]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_ip_tcp:10.0.0.3[1026]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[NTDS_LPC]
UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_http:10.0.0.3[1027]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[audit]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[securityevent]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[protected_storage]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[dsrole]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[NTDS_LPC]
UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[audit]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[securityevent]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[dsrole]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\SERVER[\\PIPE\\lsass]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[audit]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[securityevent]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[protected_storage]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[dsrole]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_ip_tcp:10.0.0.3[1026]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[NTDS_LPC]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncacn_http:10.0.0.3[1027]
UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
ncalrpc:[OLE8B33809919104CE5B44970B01637]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[wzcsvc]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[wzcsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[wzcsvc]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53
ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncalrpc:[DNSResolver]
Total endpoints found: 125
==== End of RPC Endpoint Mapper query response ====
portqry.exe -n server.apl.local -e 135 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 389 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 389 (ldap service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 389...
LDAP query response:
currentdate: 01/28/2013 14:11:54 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
UDP port 389 (unknown service): LISTENING or FILTERED
Using ephemeral source port
Sending LDAP query to UDP port 389...
LDAP query response:
currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
UDP port 389 is LISTENING
portqry.exe -n server.apl.local -e 389 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 636 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 636 (ldaps service): LISTENING
portqry.exe -n server.apl.local -e 636 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 3268 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 3268 (msft-gc service): LISTENING
Using ephemeral source port
Sending LDAP query to TCP port 3268...
LDAP query response:
currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
namingContexts: DC=apl,DC=local
defaultNamingContext: DC=apl,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
configurationNamingContext: CN=Configuration,DC=apl,DC=local
rootDomainNamingContext: DC=apl,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 1310788
supportedSASLMechanisms: GSSAPI
dnsHostName: SERVER.apl.local
ldapServiceName: apl.local:[email protected]
serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 2
forestFunctionality: 2
domainControllerFunctionality: 2
======== End of LDAP query response ========
portqry.exe -n server.apl.local -e 3268 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 3269 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 3269 (msft-gc-ssl service): LISTENING
portqry.exe -n server.apl.local -e 3269 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 53 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 53 (domain service): LISTENING
UDP port 53 (domain service): LISTENING
portqry.exe -n server.apl.local -e 53 -p BOTH exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 88 -p BOTH ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 88 (kerberos service): LISTENING
UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n server.apl.local -e 88 -p BOTH exits with return code 0x00000002.
=============================================
Starting portqry.exe -n server.apl.local -e 445 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n server.apl.local -e 445 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 137 -p UDP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
UDP port 137 (netbios-ns service): LISTENING or FILTERED
Using ephemeral source port
Attempting NETBIOS adapter status query to UDP port 137...
Server's response: MAC address 000423c733ec
UDP port: LISTENING
portqry.exe -n server.apl.local -e 137 -p UDP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 138 -p UDP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n server.apl.local -e 138 -p UDP exits with return code 0x00000002.
=============================================
Starting portqry.exe -n server.apl.local -e 139 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 139 (netbios-ssn service): LISTENING
portqry.exe -n server.apl.local -e 139 -p TCP exits with return code 0x00000000.
=============================================
Starting portqry.exe -n server.apl.local -e 42 -p TCP ...
Querying target system called:
server.apl.local
Attempting to resolve name to IP address...
Name resolved to 10.0.0.3
querying...
TCP port 42 (nameserver service): LISTENING
portqry.exe -n server.apl.local -e 42 -p TCP exits with return code 0x00000000.
Jason.
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

Migrating From Window Server 2003 to Window Server 2012 for Web server deployment and Developmemt Machine is on Window Server 2008

Hi Microsoft Team,
We need your urgent advice and that is also on priority:
Issue Description: We need to migrate from
WINDOW SERVER 2003 to WINDOW SERVER 2012 while the development activity will be carried
under WINDOW SERVER 2008 as DEVELOPMENT BOX.
.NET Framework Version: 3.5 ( For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
IIS Version: 7.5 (For both DEVLOPMENT(WINDOW SERVER 2008) and WEBSERVER(to WINDOW SERVER 2012))
Need your quick advice Is that configuration feasible for Development and
Deployment (Web Server).
Highly appreciate your response as this will depend which product we need to buy also if you feel any showstopper or concern. Please let us know.

Hi,
As suggested by Tim, in order to get better assistance, we can ask for help in the following IIS forum.
IIS Forum
http://forums.iis.net/
In addition, regarding migrating from Windows Server 2003 to Windows Server 2012, the following blog can be referred to for more information.
Step-By-Step: Active Directory Migration from Windows Server 2003 to Windows Server 2012
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
Best regards,
Frank Shen

Windows server 2012 as primary DC and DNS server and windows server 2003 as secondary DC and DNS

Migration from windows server 2003 AD DC and DNS server to windows server 2012 R2,
Cannot I set up Windows server 2012 R2 as primary DC and DNS , windows server 2003 as secondary DC and DNS ? (for backup server when server 2012 fail, user can continue to login and access internet services)

You can mix both as long as your Forest and Domain Functional level are Windows Server 2003. However, I would like to bring your attention to this blog about known problems when mixing DCs with Windows Server 2003 and 2012 R2 OS:
http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Windows Server 2003 AD Migration Problem

Hi Team,
I'm currently working on a project on Migrating our Windows Server 2003 AD server (old Machine) to our new Windows Server 2003 machine (PDC-AD). I successfully promoted our new AD server (PDC-AD) as domain controller, but upon checking, the server is not promoted
as Global catalog with following errors shown below.
C:\Documents and Settings\Administrator.PDC-AD>dcdiag /q
Warning: PDC-AD has not finished promoting to be a GC.
Check the event log for domains that cannot be replicated.
Warning: PDC-AD is not advertising as a global catalog.
Check that server finished GC promotion.
Check the event log on server that enough source replicas for the GC ar
e available.
......................... PDC-AD failed test Advertising
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... PDC-AD failed test frsevent
An Information Event occured. EventID: 0x40000617
Time Generated: 04/03/2014 11:28:47
(Event String could not be retrieved)
An Information Event occured. EventID: 0x4000062A
Time Generated: 04/03/2014 11:28:47
(Event String could not be retrieved)
An Information Event occured. EventID: 0x40000456
Time Generated: 04/03/2014 11:28:47
(Event String could not be retrieved)
......................... PDC-AD failed test kccevent
C:\Documents and Settings\Administrator.PDC-AD>\
Is there any tool I can use to further isolate the problem?.
Thanks
Mark D.

Hi Vivian,
Thanks for your reply, for additional info, I didn't use Active directory migration tool. Below is my step-by-step procedure.
1. Installed Windows Server 2003 on a new machine.
2. Promote the new Windows Server 2003 machine as a Domain controller. New Windows Server 2003 machine is promoted successfully.
3. But upon checking of the server, the new machine is not promoted as a Global Catalog.
Below are the event logs from Directory services.
1. Promotion of the local domain controller to a global catalog has been delayed because the directory partition occupancy requirements have not been met. The occupancy requirement level and current
domain controller level are as follows.
Occupancy requirement level:
6
Domain controller level:
0
The following registry key value defines the directory partition occupancy requirement level.
Registry key value:
HKeyLocalMachine\System\ CurrentControlSet\Services\NTDS\Parameters\Global Catalog Partition Occupancy
Higher occupancy requirement levels include the lower levels. The levels are defined as follows:
(0) Indicates no occupancy requirement.
(1) Indicates at least one read-only directory partition in the site has been added by the Knowledge Consistency Checker (KCC).
(2) Indicates at least one directory partition in the site has been fully synchronized.
(3) Indicates all read-only directory partitions in the site have been added by the KCC (at least one has been synchronized).
(4) Indicates all directory partitions in the site have been fully synchronized.
(5) Indicates all read-only directory partitions in the forest have been added by the KCC (at least one has been synchronized).
(6) Indicates all directory partitions in the forest have been fully synchronized.
2. The Global Catalog has no intra-site sources for at least one partition. Replication to the Global Catalog is limited to scheduled replication from inter-site sources.
Regards,

Windows Server 2003 and Microsoft Assessment and Planning tool (MAP)

Preparing for the end of support for Windows Server 2003 (4/2015) and the need to migrate from Windows Server 2003, I have been directed on several sites run the Microsoft Assessment
and Planning tool (MAP) to aid in identifying any software and hardware issues. Apparently this tool has been recently updated (7/2014) and cannot be installed on a Windows Server 2003 system. As it requires .NET Framework 4.5 to run. Unfortunately,
.NET Framework 4.5 cannot be installed on a Windows Server 2003 as it only supports .NET 4.0.x versions. All older version links to the MAP tool have been updated to link directly to version 9.1. Where can I get a MAP tool version that will run
on Windows Server 2003?

Hi,
Yes, i would agree with arnavsharma
After the environment scan has been completed in Windows Server 2008r2 or another supported OS, MAP looks at computers running earlier versions of Windows.
http://technet.microsoft.com/en-us/magazine/ee677580.aspx
Meanwhile, for the MAP related issue, you'd better ask in MAP forums:
https://social.technet.microsoft.com/Forums/en-US/home?forum=map
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Oracle XML DB WebDAV in Windows Server 2003

Hello all,
currently, we are migrating to Windows Server 2003, but when we have tried to open a WebDAV session to view the repository, Windows didn't allow it.
Please, Could anyone to help us with this issue? because I don't know how to do it.
Thanks in advance,
David.

Does it report back an error or just say does not appear to be a valid folder ( or destination)
I actually got this working on my 2k3 machine but I am trying to remeber what I did I know I disabled the internet security stuff and firewall. Try the same .
regards
coby

TS140 Windows Server 2003?

I have a customer with a new TS140 who needs to load Windows Server 2003 on the box. The reason for having to load Windows Server 2003 is a legacy piece of software that is not compatible with newer versions of Windows.
This is a TS140 70A4 001MUX model. It meets system requirements for the OS (we were able to purchase a Lenovo Enterprise Server 2003 OEM license from a liquidator) but the system is newer than any actually listed in the HCL for WIndows Server 2003
Initial attempts to install using Lenovo OEM Windows Server media results in a blue screen, unsurprising given the chronological distance between the OS media and the hardware.
EasyStartup Version 3.8.1d shipped with the server but 2008 is the earliest OS listed in the pick list. Is there an earlier version that loads drivers for this hardware for Server 2003? Failing that are there drivers that can be slipstreamed into the OS install media?
The big question: Has anyone actually installed Server 2003 on this hardware? Should I even bother trying?
Thanks for any help,
Coypu

Got a fix for you:
install Hyper-V 2012 R2 on the TS140 ( it's free!)
http://technet.microsoft.com/en-us/evalcenter/dn205299.aspx
then... install your 2003Server as a VM.
Access it through any workstation running Remote Desktop connection.
Or access if directly from the "server Core Hyper-V" machine by running the (free!) Hyper-V Tools. ( this provides a GUI, and remote desktop client)
see http://www.probus-it.se/hypervtools
another great tool for those running Hyper-V 2012 "core" (the free OS with no GUI) is the very handy A43
see http://www.a43filemanager.com/
more great tools here... http://hypervking.info/hyper-v-tools/

How to install rootsupd.exe on windows server 2003?

hello
i need to update the root certificates. but i can't use "rootsupd.exe", it's only for windows xp...
there doesn't seems to be a similar update for windows server 2003, correct?
how can i solve my problem, do i need to install the certificates manually? if yes, how does this work?
thank you very much!
best regards, jan
regards, jan

"when ich click on "rootsupd.exe" in my windows server 2003 web edition virtual machine (virtualbox), nothing happens - i can't see any actions after clicking that file... and i don't think that behavior is usual...?"
same behavior on windows 7 (x64) workstation - nothing happens after clicking.
maybe i need to extract it, and install the files manually?:
- authroots.sst
- delroots.sst
- roots.sst
- updroots.sst
regards, jan

Why the RSC can not found my JRE1.6.0.06 on windows server 2003 ?

I installed the SUN RSC program on my windows server 2003, It required JRE 1,3 or later,then I installed the JRE.16.0.06, I set the JAVA_HOME and CLASSPATH,I can got correct information with java -version commend on cmd,but the RSC still told me that it required JRE 1.3 or later.
Why ?

We run our Sun V480s and E250 (Solaris 10) headless, and depend on RSC (both CLI and GUI) to access the consoles from Windows.XP desktop machines.
We have been using the RSC GUI from the Wintel boxes quite successfully for several years, and appreciate having the RSC devices in our Sun servers. We rely on Sun's RSC software.
Several days ago we installed the current Sun JRE (1.6.0.06) on the Windows machines. RSC GUI now fails to run on the Windows machines, displaying a message box advising that Java 1.3, or later, is required and directing us to download 1.3 or later.
Since 1.6 is later than 1.3, it would appear that Sun's current JRE broke the existing Sun RSC GUI app.
How could Sun do this? WIll they release a fix?
We will try to open a Service Request, but are having difficulty due to Sun's problems implementing the new Support Contract arrangements, and it is not clear that we can access our support at this time. Sun has physically visited our facility, and given us absolute assurance that they will continue our existing contract for the duration of their difficulties, while simultaneously lapsing our contract when we attempt to access it online. Consequently, we cannot immediately get contractual assistance on this matter, through the normal support channel.
Thank you.
DG
Edited by: david_grove on Jun 4, 2008 5:53 PM

Windows Server 2003 drivers for Lenovo Essential B590

Hello, all!
I need to install a Windows Server 2003 on a Lenovo Essential B590 laptop.
Can anyone confirm there are drivers available for this OS? [see specs bellow]
Thank you for any help!
P.
Intel Pentium Processor 2020M (2M Cache, 2.40 GHz), 15.6 HD(1366x768) AntiGlare, 4GB DDR3 1600MHz(1 DIMM), 1TB / 5400rpm, Intel HD Graphics, DVD-RW, webcam 720p, NON-INTEL 1X1 BGN+BT4.0, Fingerprint Reader, Battery 6 Cell 2.2A, VGA, HDMI, 2 USB 3.0, 2 USB 2.0, 4-in-1 card reader.

Toshiba has never supported mobile computers for any version of Microsoft Servers and never offered any driver for it.
I can understand you need it but with this you are on your own but you can try to install WXP drivers but I think Satellite A500 is not even WXP supported.
It wont be easy job for you.

We're running Windows server 2003 32bit and want to migrate to Windows server 2012R2 64bit, can someone provide a step by step procedure on how to migrate instances on ADAM to AD LDS?

I have no experience in dealing with servers, but my senior has asked me to investigate on how to migrate instances on ADAM (windows server 2003 32bit) to AD LDS (Windows server 2012R2 64 bit) as in place upgrade is not an option as we're running a 32bit
Server and want to migrate to a 64bit Server. can someone please give me a Walkthrough on how to do this.
Thanks in advance.

Hi,
it'd be of great help if you could give me a step by step process of replication.
There is no step-by-step article/guide of replication process, replication between AD LDS instances of the same configuration set is an automatic process.
All we need to make sure is to create a replica of the existing instance, and there is no network/security obstacle preventing the replication.
Please note that we need to install AD LDS from Server manager on Windows Server 2012 and 2012 R2.
More information for you:
Understanding AD LDS Replication and Configuration Sets
http://technet.microsoft.com/en-us/library/cc770465.aspx
Best Regards,
Amy

Connect SQL Server 2012 from Windows Server 2003 with native client 9.0

Hi,
I currently have a setup where ETL tool Ab Intio, running on a Linux server, connects to the SQL Server 2005 through a passthrough Wintel server with Windows Server 2003 OS using SQL server native client 9.0
Now I have the requirement to upgrade the SQL server from 2005 to 2012.
My question is, will it be possible to connect to SQL server 2012 through Windows Server 2003 with native client 9.0?
As per the specs, I need native client 11.0+ to fully support SQL Server 2012, but then, as per specs, native client 11.0 doesnot run on Windows server 2003. OS upgradation is currently not on the cards.
So will it be possible to the run the basic queries we use currently, if we can connect SQL server 2012 through Windows Server 2003 with native client 9.0/10.0, without updgrading the OS of the Wintel server?
Thanking you in advance!

Hi Soumya,
Yes, you can use the SQL Server Native Client shipped with SQL Server 2005 to connect to a SQL Server 2012 instance, and there is no need to upgrade the operating system.
Regards,
Mike Yin
TechNet Community Support

DPM 2012 R2 - Windows Server 2012 R2 Hyper-v backup of Windows Server 2003 R2 - Non-retryable error 0x80070490

Hi,
I have a hyper-v host running Windows Server 2012 R2 Standard with Hyper-V on it, and on that host I got 5 virtual machines running and of those 5, 4 of those the DPM are able to backup but when DPM tries to backup a server running Windows Server 2003 R2
I get the following errors in the eventlog.
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 2013-11-28 10:46:58
Event ID: 18014
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPERV05.domain.local
Description:
Checkpoint operation for 'SERVER01' was cancelled. (Virtual machine ID 5221623F-C80C-4B92-AD02-F545D118C859)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>18014</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-11-28T09:46:58.365308800Z" />
<EventRecordID>411</EventRecordID>
<Correlation />
<Execution ProcessID="2116" ThreadID="4248" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>HYPERV05.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>SERVER01</VmName>
<VmId>5221623F-C80C-4B92-AD02-F545D118C859</VmId>
</VmlEventLog>
</UserData>
</Event>
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 2013-11-28 10:46:58
Event ID: 18012
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPERV05.domain.local
Description:
Checkpoint operation for 'SERVER01' failed. (Virtual machine ID 5221623F-C80C-4B92-AD02-F545D118C859)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>18012</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-11-28T09:46:58.365308800Z" />
<EventRecordID>412</EventRecordID>
<Correlation />
<Execution ProcessID="2116" ThreadID="4248" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>HYPERV05.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>SERVER01</VmName>
<VmId>5221623F-C80C-4B92-AD02-F545D118C859</VmId>
</VmlEventLog>
</UserData>
</Event>
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 2013-11-28 10:46:58
Event ID: 10150
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPERV05.domain.local
Description:
Could not create backup checkpoint for virtual machine 'SERVER01': Element not found. (0x80070490). (Virtual machine ID 5221623F-C80C-4B92-AD02-F545D118C859)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>10150</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-11-28T09:46:58.365308800Z" />
<EventRecordID>413</EventRecordID>
<Correlation />
<Execution ProcessID="2116" ThreadID="4280" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>HYPERV05.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>SERVER01</VmName>
<VmId>5221623F-C80C-4B92-AD02-F545D118C859</VmId>
<Parameter0>%%2147943568</Parameter0>
<Parameter1>0x80070490</Parameter1>
</VmlEventLog>
</UserData>
</Event>
What I have done to try to troubleshoot this issue is:
Reinstalled DPM - No sucess
Restarted the Hyper-v Host - No sucess
I'm at the point where I am out of ideas and google hasn't given me much.
/Joseph

i have the same error.
"vssadmin list writers" shows last error unknown for all writers
disk space is sufficient
ntbackup of systemdrive and systemstate runs fine.
i installed KB940349 which fixes some vss related issues but the problem is still there.
any ideas?
Thanks.
When you have vssadmin reporting unknown error the only way to reset the vsswriters (as I understand it please correct me if I'm wrong :) ) is to restart the machine. The Fellenator is correct, make use that the vsswriter is working correctly since this
is the main function DPM is using when taking backup. He's also right in saying that it's outside the scope! Create a new thread on your error, then you will get much better responce!
/Joseph

Migrate oracle 10.2.0.5.0 enterprise on windows server 2003 32bit to Linux

Hello,
I am trying to find any white paper regarding the benefits of migrating oracle database from windows server 2003 32bit
to RedHat linux server 64bit.
The current db version on windows is 10.2.0.5.0
The new version on linux will be 11.2.0.3.0
If anyone crossed such a white paper describing the pros & cons for such a migration..
Thanks alot.
Edited by: user7320646 on Jan 9, 2013 5:45 AM

John makes some very good points but I would like to clarify one thing from his post: you are planning three migrations:
1. From 32bit -> 64bit
2. From Windows to Linux
3. From Oracle 10gR2 to 11gR2
The second of these is the one most liekly to give you grief. You certainly should not attempt to combine it with a database upgrade. Either move the database to RHEL and then upgrade it, or upgrade it on Windows and then move it to the new server.
Of these, the first is the least controversial. So it's a nice point whether it is worth upgrading from Windows 32bit to Windows 64bit prior to moving to Linux.
Cheers, APC

Migration on windows server 2003 to 2012 r2 by using IIS 6.0 what are parameters are changed means supported and non suported parameters and configurations?

Similar Messages

Maybe you are looking for