Problems after print server migration to Windows Server 2008 R2

Hi all,
New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
Environment
I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
Problems
Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
Attempted Fixes
These are some of the attempted fixes that I have tried:
Turning it off and on
Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
Upgrading the firmware on the CM3530's to resolve garbled printing
Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
If anyone is able to provide any assistance that would be greatly appreciated.
Many thanks,
Hartz.
tldr; our printers are screwed since migrating to Windows Server 2008 R2.

Hi all,
New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
Environment
I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
Problems
Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
Attempted Fixes
These are some of the attempted fixes that I have tried:
Turning it off and on
Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
Upgrading the firmware on the CM3530's to resolve garbled printing
Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
If anyone is able to provide any assistance that would be greatly appreciated.
Many thanks,
Hartz.
tldr; our printers are screwed since migrating to Windows Server 2008 R2.

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

  • Webi scheduling error in BO 4.0 SP04 after security patch updates in windows server 2008 R2

    We are getting  below error in BO 4.0 SP04 Web Intelligence report scheduling after security patch updates in windows server 2008 R2
    while trying to invoke the method com.businessobjects.sdk.core.server.IServer.getServerContext() of an object returned from com.businessobjects.rebean.wi.impl.services.DocumentInstanceManagementServiceImpl.getServer(com.businessobjects.sdk.core.context.IContext, com.businessobjects.rebean.wi.model.engine.IDocumentInstance)
    We have reverted back security patch but still giving above scheduling problem in  BO 4.0 SP04 WebI and we can view and refresh report.
    Is there any way to fix the scheduling problem in BO 4.0 SP04 WebI?

    HI,
    Check SAP notes if they will help you.
    1934855 - Scheduled Web Intelligence documents fail with com.businessobjects.sdk.core.server Error
    1916443 - Scheduling Web Intellignce reports which are having long names to excel and pdf fails.
    1792921 - Unable to schedule Webi documents in Excel or PDF format

  • Problem starting Repository Browser Service on Windows Server 2008

    Using the default Warehouse Builder installation in the 11g (11.1.0.7.0) databaseinstallation on a clean Windows Server 2008 64-bit installation.
    Warehouse Builder installed and populated ok, OWB client works fine etc.
    When trying to start the Repository Browser listener by running the startOwbbInst.bat, the OC4J container crashes with the following error in the \owb\j2ee\log\oc4j\log.xml:
    +<MSG_TEXT>Could not create Secure http listener due to {0}</MSG_TEXT>+
    +<SUPPL_DETAIL><![CDATA[java.io.FileNotFoundException: C:\Oracle\product\11.1.0\db_1\owb\bin\admin\..\..\j2ee\config\%ORACLE_HOME%\owb\j2ee\config\keystore.jks (The system cannot find the path specified)+
    +     at java.io.FileInputStream.open(Native Method)+
    +     at java.io.FileInputStream.<init>(FileInputStream.java:106)+
    +     at java.io.FileInputStream.<init>(FileInputStream.java:66)+
    +     at oracle.oc4j.security.OC4JSSLSocketFactory.getStoreIn(OC4JSSLSocketFactory.java:253)+
    (The local_service_login.bat works fine).
    We're starting this as an administrator user in Win2008.
    All parameteres in the setowbenv.bat seems to be correct as far as I can tell. There is a strange reference to %ORACLE_HOME% in the above log, of which I've no idea where it is coming from....
    Identical installation worked fine on a 64-bit Windows Server 2003, - so can this be something related to a new security model in Windows Server 2008?
    (I found a posting regarding problems with the startOwbbInst.bat on Vista  [here |http://forums.oracle.com/forums/thread.jspa?messageID=2275781&#2275781] - so maybe.... however, the quickfix mentioned there did'nt help us here...)
    Anyone experienced similar problems (and preferably solved them) on Windows Server 2008 and/or Vista?
    Regards,
    -Haakon-

    Solved this after some trawling through xml configuration files on the server.
    The file C:\Oracle\product\11.1.0\db_1\owb\j2ee\config\http-web-site.xml contains the reference to keystore.jks:
              <ssl-config keystore="*%ORACLE_HOME%*/owb/j2ee/config/keystore.jks" keystore-password="-&gt;keystoreadmin"/>
    changing this to:
              <ssl-config keystore="C:\Oracle\product\11.1.0\db_1/owb/j2ee/config/keystore.jks" keystore-password="-&gt;keystoreadmin"/>
    and the OC4J container starts successfully.
    Regards,
    -Haakon-

  • Migration of Windows Small Business Server 2003 to Windows Server 2012 Essentials

    Hi,
    I am trying to migrate Windows Small Business Server 2003 to Windows Server 2012 Essentials by following the steps given in the link below:
    http://technet.microsoft.com/en-us/library/jj200112.aspx
    I have looked at other threads on the forum but none of them have been too helpful.
    The issue: When
    I run the Migration Preparation Tool on the Source Server, it runs successfully and does not report any errors. However, when I try installing Windows Server 2012 Essentials on the Destination Server, it displays an error that says 'Source
    Server not prepared for migration: After you run the Migration Preparation Tool successfully on your source Server, click retry'.
    The Source Server has 2 network adapters-one for the local network and the other for connection to the internet and the router is set as the default gateway this adapter.
    Since it is mentioned in the documentation - 'configure your Source Server to use one network adapter', I'm wondering if this is the issue and I need to make changes in this configuration? 
    On running the Microsoft IT Environment Health Scanner tool it
    reported an error - 'DNS Server listening on multiple addresses' and a warning ‘Domain Controller listening on multiple addresses’. Both point to the same solution KB 272294 (http://support.microsoft.com/kb/272294).
    But it did not remove the errors.
    Other steps performed:
    As per the steps, I performed a backup, installed recent service packs and synchronized the source server time with external source.
    On running the Best Practices Analyser. It shows 3 warnings.
    - The threshold for the Allocated Memory alert is set to the default value. However the server has more than 2 GB of RAM installed.
    - Microsoft Outlook Client not installed" Text="Microsoft Outlook Client is not installed in the ClientApps folder. You must run Windows SBS integrated setup.
    - The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000. The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000.
    I also ran the Ran netdiag.exe, dcdiag.exe commands
    and no failures were reported.
    The Event Viewer does not show any errors.
    Not sure to what extent these warnings would affect the migration. 
    Any help would be appreciated. Thanks!

    The SBS2003 needs to use one NIC only so you'll need to change that before starting. If it is the premium version and has ISA server installed, that will need to be removed first.  See:
    http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx
    -- Al

  • Problems with Microsoft.Update.Session on Windows Server 2012R2

    Hi, I've created a script for collecting Windows Update information using the "Microsoft.Update.Session" comObject.
    I got some problems collecting data from certain servers, but I don't understand what can be wrong.
    In this example I got "DC1" and "DC2", where DC1 is a Windows 2012R2 Core, and DC2 is a Windows 2008R2. Both has installed updates previously.
    The problem is that the Microsoft.Update.Session won't return the installed updates from "DC1", using the identical commands as on "DC2".
    Commands used in this example:
    $updateSession = New-Object -ComObject Microsoft.Update.Session
    $Searcher = $updateSession.CreateUpdateSearcher()
    $PendingUpdates = $Searcher.Search("IsInstalled=0 and Type='Software' and IsHidden=0")
    $PendingUpdates = $PendingUpdates.Updates
    $Installed = $Searcher.QueryHistory(0,1) | select -ExpandProperty Date
    Output from session DC1:
    Windows PowerShell
    Copyright (C) 2014 Microsoft Corporation. All rights reserved.
    PS C:\Users\User> Enter-PSSession -ComputerName DC1 -Credential User
    [DC1]: PS C:\Users\User\Documents> $updateSession = New-Object -ComObject Microsoft.Update.Session
    [DC1]: PS C:\Users\User\Documents> $Searcher = $updateSession.CreateUpdateSearcher()
    [DC1]: PS C:\Users\User\Documents> $PendingUpdates = $Searcher.Search("IsInstalled=0 and Type='Software'
    and IsHidden=0")
    [DC1]: PS C:\Users\User\Documents> $PendingUpdates = $PendingUpdates.Updates
    [DC1]: PS C:\Users\User\Documents> $Installed = $Searcher.QueryHistory(0,1) | select -ExpandProperty Date
    [DC1]: PS C:\Users\User\Documents> $Installed
    [DC1]: PS C:\Users\User\Documents> $Searcher.QueryHistory(0,5)
    [DC1]: PS C:\Users\User\Documents>
    Output from session DC2:
    PS C:\Users\User> Enter-PSSession -ComputerName DC2 -Credential User
    [DC2]: PS C:\Users\User\Documents> $updateSession = New-Object -ComObject Microsoft.Update.Session
    [DC2]: PS C:\Users\User\Documents> $Searcher = $updateSession.CreateUpdateSearcher()
    [DC2]: PS C:\Users\User\Documents> $PendingUpdates = $Searcher.Search("IsInstalled=0 and Type='Software'
    and IsHidden=0")
    [DC2]: PS C:\Users\User\Documents> $PendingUpdates = $PendingUpdates.Updates
    [DC2]: PS C:\Users\User\Documents> $Installed = $Searcher.QueryHistory(0,1) | select -ExpandProperty Date
    [DC2]: PS C:\Users\User\Documents> $Installed
    16. oktober 2014 01:06:52
    [DC2]: PS C:\Users\User\Documents> $Searcher.QueryHistory(0,5)
    Operation : 1
    ResultCode : 2
    HResult : 0
    Date : 16.10.2014 01:06:52
    UpdateIdentity : System.__ComObject
    Title : Security Update for Windows Server 2008 R2 x64 Edition (KB3000869)
    Description : A security issue has been identified in a Microsoft software product that could affect your syste
    m. You can help protect your system by installing this update from Microsoft. For a complete list
    ing of the issues that are included in this update, see the associated Microsoft Knowledge Base a
    rticle. After you install this update, you may have to restart your system.
    UnmappedResultCode : 0
    ClientApplicationID : AutomaticUpdates
    ServerSelection : 1
    ServiceID :
    UninstallationSteps : System.__ComObject
    UninstallationNotes : This software update can be removed by selecting View installed updates in the Programs and Featu
    res Control Panel.
    SupportUrl : http://support.microsoft.com
    Categories : System.__ComObject
    Operation : 1
    ResultCode : 2
    HResult : 0
    Date : 16.10.2014 01:06:38
    UpdateIdentity : System.__ComObject
    Title : Security Update for Microsoft .NET Framework 4.5, 4.5.1 and 4.5.2 on Windows 7, Vista, Server 200
    8, Server 2008 R2 x64 (KB2972107)
    Description : A security issue has been identified in a Microsoft software product that could affect your syste
    m. You can help protect your system by installing this update from Microsoft. For a complete list
    ing of the issues that are included in this update, see the associated Microsoft Knowledge Base a
    rticle. After you install this update, you may have to restart your system.
    UnmappedResultCode : 0
    ClientApplicationID : AutomaticUpdates
    ServerSelection : 1
    ServiceID :
    UninstallationSteps : System.__ComObject
    UninstallationNotes : This software update can be removed by selecting View installed updates in the Programs and Featu
    res Control Panel.
    SupportUrl : http://support.microsoft.com
    Categories : System.__ComObject
    Operation : 1
    ResultCode : 2
    HResult : 0
    Date : 16.10.2014 01:04:30
    UpdateIdentity : System.__ComObject
    Title : Security Update for Windows Vista, Windows 7, Server 2008, Server 2008 R2 (KB2917500)
    Description : Install this update to resolve an issue which requires an update to the untrusted certificate sto
    re on Windows systems and to keep your systems up to date. After you install this update, you may
    have to restart your system.
    UnmappedResultCode : 0
    ClientApplicationID : AutomaticUpdates
    ServerSelection : 1
    ServiceID :
    UninstallationSteps : System.__ComObject
    UninstallationNotes :
    SupportUrl : http://support.microsoft.com
    Categories : System.__ComObject
    Operation : 1
    ResultCode : 2
    HResult : 0
    Date : 16.10.2014 01:04:30
    UpdateIdentity : System.__ComObject
    Title : Security Update for Microsoft .NET Framework 4.5, 4.5.1 and 4.5.2 on Windows 7, Vista, Server 200
    8, Server 2008 R2 x64 (KB2979578)
    Description : A security issue has been identified in a Microsoft software product that could affect your syste
    m. You can help protect your system by installing this update from Microsoft. For a complete list
    ing of the issues that are included in this update, see the associated Microsoft Knowledge Base a
    rticle. After you install this update, you may have to restart your system.
    UnmappedResultCode : 0
    ClientApplicationID : AutomaticUpdates
    ServerSelection : 1
    ServiceID :
    UninstallationSteps : System.__ComObject
    UninstallationNotes : This software update can be removed by selecting View installed updates in the Programs and Featu
    res Control Panel.
    SupportUrl : http://support.microsoft.com
    Categories : System.__ComObject
    Operation : 1
    ResultCode : 2
    HResult : 0
    Date : 16.10.2014 01:03:20
    UpdateIdentity : System.__ComObject
    Title : Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 fo
    r x64-based Systems (KB2968294)
    Description : A security issue has been identified in a Microsoft software product that could affect your syste
    m. You can help protect your system by installing this update from Microsoft. For a complete list
    ing of the issues that are included in this update, see the associated Microsoft Knowledge Base a
    rticle. After you install this update, you may have to restart your system.
    UnmappedResultCode : 0
    ClientApplicationID : AutomaticUpdates
    ServerSelection : 1
    ServiceID :
    UninstallationSteps : System.__ComObject
    UninstallationNotes : This software update can be removed by selecting View installed updates in the Programs and Featu
    res Control Panel.
    SupportUrl : http://support.microsoft.com
    Categories : System.__ComObject
    [DC2]: PS C:\Users\User\Documents>
    Anyone got an idea of what might be wrong?
    Thanks!

    Hi Objectclass,
    The updates you query from DC1 (Windows Server core 2012 r2) is different from DC2 (Windows Server 2008 R2), because firstly these two servers have different operating system versions so they apply different updates, and DC1 also have less updates than DC2
    because of server core edition.
    Fewer installed features means fewer features to patch and maintain, Server Core has been available since Windows Server 2008, and historically we've noted as much as 35-45% fewer patches needed on Server Core installations.
    Refer to:
    http://blogs.technet.com/b/keithmayer/archive/2012/10/19/improved-taste-less-filling-more-uptime-server-core-in-windows-server-2012-31-days-of-favorite-features-in-winserv-2012-part-19-of-31.aspx
    If there is anything else regarding this issue, please feel free to post back.
    If you have any feedback on our support, please click here.
    Best Regards,
    Anna Wang
    TechNet Community Support

  • 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

  • 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

  • Migration from windows server 2008 10.2.0.4 to linux as4 11.2g

    Hello,
    I am looking to migrate my 10.2.0.4 which is on windows server 2008 to 11gr2 which is on linux as 4.. my database size is 50gb, what is best way to perform this task, please do update me, i will be thankfull to you.
    Thanks and regards
    firdous

    Hi,
    Please close this thread as answered and keep updating your other thread:
    migration from windows server 2008 10.2.0.4 to linux as4 11.2g
    Regard
    Helios

  • Exchange Server 2013 In Windows Server 2012 - unable to logon EXchange Administrator Center (EAC)

    Hi All,
    I Just installed Exchange Server 2013 in Windows Server 2012 and trying to connect Dynamics CRM 2013 (DNS).
    The Installations Success full but unable to load the EAC page by using the following URL
    https://servername:port/owa/auth/logon.aspx
    I have cross checked in Exchange/owa/auth folder don't have the "logon.aspx" file 
    But the auth folder have the "logoff.aspx" 
    I installed many time freshly in separate WS-2012 but it not contains that logon.aspx 
    I want access the Exchange Administrator Center 
    Please Help me to solve it 
    IIS Exchange (Missing of logon.aspx)
    SRKD0808

    Hi All,
    I sorted out this problem 
    Actually we have to run these 2 commands in Domain Control, But what i did  I just run this
    1) setup /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Command in Domain Control we don't need to run the 2nd command, Because I already try to installed exchange 2013 very first time it success and after some modifications
    it gone.
    That time it will ask you to provide Organization name, Once you give that it will create the Organization name in Domain control and it will save the settings when
    you install first time 
    Because of this reason It is failing to run these 2 command
    Finally what i did I just revert back my Domain control snapshot & Exchange server as well 
    Then i started freshly Installation in DC and Exchange server 2013 successfully installed 
    URL http://servername/ecp/default.aspx
    Whole Process will be here 
     Exchange Server 2013 Step by Step Installation In Windows Server 2012
    SRKD0808

  • Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working

    Hi all,
    I installed SharePoint server 2013 on Windows  server 2012 R2 using VirtualBox.  I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
    the DC server.  Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
    admin page, it gives error info:
    System status:  The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
    a good state and try again.
    Search Application Topology:  Unable to retrieve topology component health states. This may be because the admin component is not up and running.
    From event viewer, I see following errors:
    (1) Error From source: SharePoint Server
    Application Server Administration job failed for service instance  Microsoft.Office.Server.Search.Administration.SearchServiceInstance
    (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The object you are trying to create already exists. Try again using a different name.  
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.  
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
    isAdministrationServiceJob)
    (2) Error From source: SharePoint Server Search
    Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
    Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
    (3) Warning from source: SharePoint Server Search
    A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description:  Error ordinal: 1 Message:
    Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2    at
    System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
    (4) Error From source: SharePoint Server
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
    (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.  
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
    been upgraded.  
    Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
    Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
    Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    This seems also to be a SP set up issue.
    Thanks a lot.

    Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
    Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
    Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
    $IndexLocation = "C:\Search"  #Location must be empty, will be deleted during the process!
    $SearchAppPoolName = "SSAPool"
    $SearchAppPoolAccountName = "mydomain\admin"
    $SearchServiceName = "SSA"
    $SearchServiceProxyName = "SSA Proxy"
    $DatabaseServer = "W12R2DC1"
    $DatabaseName = "SSA"
    $spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
    if (!$spAppPool)
     $spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
    $ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
    if (!$ServiceApplication)
    # process stays at the following step forever, already one hour now.  
    $ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer  $DatabaseServer -DatabaseName $DatabaseName
    Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
    (1) Crawler:Content Plugin under source Crawler:Content Plugin 
    Content Plugin can not be initialized - list of CSS addresses is not set.
    (2) Warning for SharePoint Server Search
    A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description:  Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2   
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
    (3) Error for SharePoint Server Search
    Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
    Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
    (4) Error for SharePoint Server
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded. 
    (5) Error Shared Services for SharePoint Server Search 
    Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
    Reason: The object you are trying to create already exists. Try again using a different name. 
    Technical Support Details:
    System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name. 
       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
    Above errors keep being generated. Last step for SSA creation stay there forever.  Any clue what is really going on?  Thanks.

  • How do I run a non-server program on Windows Server 2008

    I currently run a synchronization software application on my desktop in order to backup and synchronize over 600GB of data.  I would like to install this on our server, which runs Windows Server 2008, but the software does not provide for installation
    on this operating system.  I continue to receive a message stating that the software may not run properly on Windows Server OS, but it does not allow me to bypass this message.  Is there any way to create a partition or trick the software into thinking
    that it is running on a different operating system or do I have to abandon Server 2008 and install a basic home operating system in order to run this software?  Any help would be tremendously appreciated.  
    Thanks!
     

    Hi,
    According to your description, my understanding is that you want to install an software which is not supported by Windows Server.
    Try to install this software in other compatibility mode:
    1. Right-click the installation program and select properties.
    2. Select Compatibility tab, select the checkbox Run this program in compatibility mode for.
    3. try to use different OS to install this program.
    Besides, you may right-click the installation program and select Run as administrator.
    Above are my personal suggestion and just for your reference. If the problem still exit, I suggest you to connect the software‘s support/form for better help.
    If you want to backup date, I suggest you to use Windows Server Backup, you may reference the link below for detailed information:
    http://technet.microsoft.com/en-us/library/cc770757.aspx
    Best Regards,           
    Eve Wang     

  • How to enable high availability on SQL Server 2005 with Windows Server 2008 Enterprise R2

    Dear Folks,
    I would like to ask you about this thing. I'm working for IT department for bank in Myanmar. Our bank have up to 96 branches across all of Myanmar including H.O. We are using Microsoft SQL Server 2005 with Windows Server 2008 for our banking
    information system. My main problem is having to backup and restore the database backup files every time the servers in branches goes down for whatever reasons. I want to deploy this feature of high availability and failover cluster using Windows Server 2008
    and SQL Server 2005. Our branches have 2 Servers. One is for Primary and other is for Backup. What I want to do is that, I want to change Backup Server to Primary Server whenever the Primary Server goes down for whatever reasons. All the working data and databases
    from Primary will immediately replicated into Backup Server along with all the IP information of Primary Server. Please give me step by step guide for this process.

    Try below
    http://blogs.msdn.com/b/cindygross/archive/2009/10/23/checklist-for-installing-sql-server-2005-as-a-clustered-instance.aspx
    I will recommend you to upgrade SQL server to newer version for support as well as flexibility.
    Regards,
    Vishal Patel
    Blog: http://vspatel.co.uk
    Site: http://lehrity.com

  • WSUS server role on Windows Server 2012 R2 - Supported SQL Configurations

    According to
    this page the supported SQL configurations for WSUS on Windows Server 2012/2012 R2 stop at SQL Server 2012 SP1, but there is no mention of SQL Server 2012 SP2 being supported.
    However, both the SCCM 2012 R2
    supported configuration page and this announcement state that SQL Server 2012 SP2 is fully supported on SCCM 2012 R2 with no
    known limitations. Bearing in mind a big part of SCCM is to perform software updates which in turn requires WSUS to be installed...
    ... Is SQL Server 2012 SP2 supported on WSUS 4.0 (aka WSUS server role on Windows Server 2012 R2)?

    The only thing that mattered for the versions mentioned on TechNet probably is the date the articles are published. I'm no Microsoft employee so I cannot guarantee you support even if I trace back some Microsoft article that explains the lifecycle of MS
    products and support.
    Fact is that MDT uses a database, SQL is a database server. SQL server has all kinds of compatibility modes to support databases dating multiple versions back.
    Another fact is that a Service pack is an
    update to the software (be it a large one) Microsoft will not break compatibility with their own products (and may others that relay on SQL server) by an update.
    And a last fact is that in general, updates are required when you need support. After all, updates fix issues, and engineers generally don't like ghosthunting a bug that has already been patched.
    MCP/MCSA/MCTS/MCITP

  • How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

    I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
    single Windows Server Failover Cluster (WSFC) that spans two data centers.
    If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
    I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
    If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
    Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

    please post you question on failover clusters in the cluster forum.  THey will explain how this works and point you at scipts.
    You should also look in the Gallery for cluster management scripts.
    ¯\_(ツ)_/¯

Maybe you are looking for