New server 2012 - some NT4 /98/W2K clients

Hi,
Have a bit of a challenge here.... I have a scenario were we are running a full 2003 AD with 2003R2 DC and a couple of virtual servers...
Time has come to move forward and upgrade to 2012 seems like the only option using Hyper-V. The particular scenario has a big challenge: more than 50 machines with legacy machines running from NT4, Windows 98, Windows 2000 pro...
Getting rid of these machines is just not an option. They will have to dump data to shared folders with lots of security permissions configured.
Will NT4 be able to authenticate to 2012 DC (I would be very surprised)? If not,
Should I create  a new domain and leave the machines authenticating on the old domain.
Would a trust work 2003 <--> 2012?
If a trust works, What would be the minimum AD level on the 2012 server?
The challenge is really to have a modern infrastructure running Hyper-V for the more modern clients, but, at the same time, to keep those really old machines running...
Thanks for sharing your ideas on this!

Hi
This is tricky, for sure you will not have definite answer, and for sure you will encounter some problems, i know this from same case but with server 2008 dc, i recommend that you set up lab and test it thoroughly.
Getting rid of these machines is just not an option? 
Why, maybe this is the easiest and best way to go. Probably someone should have done it long ago
Yes you can create  a new domain and leave the machines authenticating on the old domain, but that i think will just prolong inevitable, saying bye to the old os's.
Yes you can create trust between server 2003 domain and server 2012 domain
http://technet.microsoft.com/en-us/library/cc738955(v=ws.10).aspx
Windows Server 2012 requires a Windows Server 2003 forest functional level
http://technet.microsoft.com/en-us/library/cc771294.aspx
And at last you can't have modern infrastructure and at the same time have those really old machines running... :)

Similar Messages

  • New Server 2012 -- Network Location Awareness & Power Failure

    Could you try setting up a dependency or delay on the boot? This would be more of a temporary solution, but should help you confirm that the only issue was with communication with the DC.

    Hello everyone,This is kind of a mixed question of AD/Domain/GPO, Server 2012 R2 Standard, Windows 7 clients, and File Sharing.. please bare with me.We had an interesting event this morning..We have a 2012 R2 STD member file server on the domain. We had a total power failure, and I believe the file server came up faster than any domain controller. Anyhow, we couldn't access the shares on the server. Upon further investigation, I saw that the network location on the file server was 'unknown' and decided to restart the server. After that, it went back to its domain profile.Are there any known solutions to this scenario? Can I force the server to use the domain profile at all times? I've briefly read about the local GP edit trick, but haven't tried it out yet. Apparently, you can allow changes to adapter profiles, and then manually set...
    This topic first appeared in the Spiceworks Community

  • The MS15-10 Security Update for Windows Server 2012/R2 Essentials and the Client Restore Functionality

    The MS15-10 Security Update for Windows Server 2012/R2 Essentials and the Client Restore Functionality - The Windows Server Essentials and Small Business Server Blog - Site Home - TechNet Blogs:
    http://blogs.technet.com/b/sbs/archive/2015/03/13/the-ms15-10-security-update-for-windows-server-2012-r2-essentials-and-the-client-restore-functionality.aspx
    FYI

    Hi Susan.  I hope there's a better 'fix' coming to replace this "uninstall the updates, restore, then reinstall the updates after the restore".  This kind of workaround requires that all of us remember that there's a problem
    with KB3023562 and KB3004375 from now until the end of WS2012E.  Not sure I'll remember this 6 months from now when the problem crops up during a restore.   -:(
     Merv Porter
    =========================

  • Push Data From Sql server 2012 (Express) to Sql Server 2012 (Standard) (i.e. Client to Server)

    Hi all,
    I’m new to this new idea /task/work.
    My Idea: To push data to server (Sql Server 2012 Standard or Enterprise Edition).
    What I’m having? :
    1.A server pc (Windows  Server 2012 + Sql Server 2012 Standard or Enterprise Edition installed).
    2.Two or three Client pc in number (lets us say Windows Server 2012 + Sql Server 2012 with Express Edition installed).
    3.These 3  machines (1 server + 2 client pc) are in communication with one and another(LAN).
    4.Assume that, I'm having one database let us say “Company_DB” with single table “Tbl_Employee”(as of now) in server and similarly in both reaming client PC too.
    i.e.
    Server is having Company_DB (Database), is having table Tbl_Employee
    Client A is having Company_DB (Database) , is having table
    Tbl_Employee
    Client B is having  Company_DB (Database) , is having table
    Tbl_Employee
    What I did ?:
    Step 1: Suppose that, today I entered/created  10 employee details in Client A (say 1 to 10).
    Step 2: On the next day, I created some more employees (say 5 employees i.e 1 to 5)
     in Client B.
    What I need?
    I need to push/send/store these records (i.e. total 15 employees details) should be present in my SERVER PC.
    I googled for the same, found some suggestions like SSIS or
    Import/Export wizard etc…
    How can I achieve this?, and this should happen for some regular intervals like 3/5 hours without any duplicate data.

    sounds like Merge replication to me
    http://www.databasejournal.com/features/mssql/article.php/1438231/Setting-Up-Merge-Replication-A-Step-by-step-Guide.htm
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • New Server 2012 install - Active Directory not working properly

    We recently converted from 2003 to 2012. Our 2012 R2 server seems to be running fine. We did a DCPROMO on the OLD 2003 DC just fine but now there are all sorts of odd errors (Sharepoint can't authenticate users, Can't run Exchange 2013 on another 2012 server
    because it can't find AD, etc.)
    on the DC we have a Group Policy error 1096. "Group Policy Object LDAP://CN=User,cn={2B476B3E-2749-4B1B-8EC1-F5672A66F94F},cn=policies,cn=system,DC=mydom,DC=local\\mydom.local\SysVol\mydom.local\Policies\{2B476B3E-2749-4B1B-8EC1-F5672A66F94F}\User\registry.pol"
    So far I haven't found anything on how to fix this (and the AD itself.) There are some errors in the DCDIAG log, too:
          Starting test: NetLogons
             Unable to connect to the NETLOGON share! (\\ISD-DC1\netlogon)
             [ISD-DC1] An net use or LsaPolicy operation failed with error 67,
             The network name cannot be found..
    Starting test: FrsEvent
             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.
    Any suggestions how we can fix these errors are greatly appreciated!

    Hi,
    Did you migrate the Active Directory from Windows server 2003 to Windows server 2012?
    Please refer to this article:
    https://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
    Regards.
    Vivian Wang

  • Windows Server 2012 Essentials (not R2) - all client computers offline

    The server is Windows Server 2012 Essentials (not R2). I have had this problem ever since I first installed the Windows Server 2012 Essentials server in the summer of 2013 (before R2 was released). The Windows Server 2012 Essentials server shows offline
    for all Devices under Dashboard. (Allow me to add that I just installed another site with Windows Server 2012 Essentials R2, and it was a breeze - all of the computers at the second install site are online.) I have one Windows 8.1 Pro client and the rest
    are Windows 7 Pro clients. The problem occurs on ALL client computers.
    I have removed computers from Devices in Dashboard on the server, rebooted the server, changed the client computer to a workgroup, rebooted the client computer, and reinstalled the connector software on the client computer. Same result. I
    have tried this on a Windows 7 Pro client and a Windows 8.1 Pro client with the same results.
    After running the connector on a client computer and waiting for the server to update its Devices status, if I look under Devices on the server Dashboard, the Windows 8.1 client computer will say online but within 24 hours it goes offline again. The
    Windows 7 client computers never show online. Both computers stay offline - they NEVER show an online status (referring to the status under Devices in Dashboard).
    I should make it clear that the clients can access the server shares with no problem. File synchronization works great. The clients can ping the server and the server can ping the clients. But client backups on the server fail.
    One of the most troublesome things about this problem is that it prevents the client computers from being accessed remotely using the website setup by Anywhere Access. I can login to get remote access to the shared files on the server, but
    the only computer that says "online" is the server. All of the other computers are "offline".
    The server and clients are only using Windows firewall. The clients all use Microsoft Security Essentials for their anti-virus.
    I used a troubleshooting tool that tells me that there are problems with port 6602 on the server, but the clients are all fine with port 6602. I know port 6602 is important for using Anywhere Access but I am still trying to find out more details on that.
    I have checked all of the firewall settings related to port 6602 on the server, and the firewall settings look like the standard Windows settings for this port. I used netstat to find the PID associated with the port, and I looked up the PID to find the service.
    That all looked standard, too.
    I have been working on this problem since the summer of 2013!! Does anyone have ANY suggestions?!!
    HELP!

    Hi,
    Just addition, please check if all necessary Windows updates are installed on those
    “Offline” client computer.
    When connect client computers to the Windows Server 2012 Essentials server by using the Connector software, there
    will be LAUNCHPAD on the client computer. Was this LAUNCHPAD grayed out? Please check if can access Shared Folders via this LAUNCHPAD. Meanwhile, please ping the Windows Server 2012 Essentials via IP address and server name when client computers show as
    Offline. Any find?
    Get Connected in Windows Server Essentials
    In addition, please follow the path on Server and client computer:
    %programdata%\Microsoft\Windows Server\Logs. Did you check any relevant Server-side logs and
    Client-side Logs if find more clues?
    Windows
    Server Essentials 2012/2012 R2 Log Files
    If any update, please feel free to let us know.
    Hope this helps.
    Best regards,
    Justin Gu
    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]

  • New Server 2012 R2 server to take over for 2008 R2 - confused about alias necessity

    Hello,
    Have Server 2008 R2 running in a small environment (35 users).  It was time to get new hardware and it has been setup with Server 2012 R2.  Already promoted to DC and running DNS.  Ready to transfer FSMO roles over to the 2012 R2 server. 
    My concern/confusion comes here:
    Users have network drives mapped to old server (i.e.
    \\dc1\share)
    New servername is for instance "dc2"
    Do I demote dc1, remove it from the environment and create an alias named dc1 pointing to dc2, thus, networked drives and network printer shares continue to work, or is there a better way to do this?
    thanks

    imho just update mapped drives using gpo and that's all
    if you have just one server for all stuff, don't demote old one , keep 2 servers alive (if you can, I don't know, maybe you need give old one away) and you will have redundancy. Then if you got 2 servers do DFS shares (shares will have names not bind
    to servers name so you can add, replace server's with no problems and have redundancy of shared folders too)

  • Server 2012 R2 DirectAccess - 2008 R2 Client

    I have things working for Server 2012 R2 Direct Access and Windows 8.1 Enterprise machines. Now moving on to Server 2008 R2 as a client, the environment is not working.
    I just tried turning on Windows 7 support and applying but still no luck.  I am not seeing much on this, so I suspect it usually just works for Server 2008 R2?
    Mike

    So I forged ahead with an actual fresh Windows 7 machine, all service packed up, instead of the existing 2008 R2 machine that we need to keep for sometime.
    I've installed the DCA 2.0, made the Group Policy edits on the domain.  The Windows 7 machine has received the updates and DCA appears happy when on the private network.
    However when the Windows 7 machine is switched over to the public network, no connection.  Not really much of a hint as to what the problem is.
    RED: Corporate connectivity is not working.
    "Your computer cannot connect to the DirectAccess server. If the problem persists, contact your administrator.
    The Probes FAIL, DTEs FAIL.
    The 2012 R2 DirectAccess server has no knowledge of the failed connection attempts.
    This is quite the challenge... 
    Mike

  • Adding new server 2012 DC in existing 2003 forest

    the prerequisites check fails. here is the content of the log file. please help me fix it.
    [2012/12/27:16:27:25.535]
    Adprep created the log file 'C:\Windows\debug\adprep\logs\20121227162725-test\ADPrep.log'
    [2012/12/27:16:27:25.535]
    Adprep successfully initialized global variables.
    [Status/Consequence]
    Adprep is continuing.
    [2012/12/27:16:27:25.545]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Schema,CN=Configuration,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.545]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.545]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=AD01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.546]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.546]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Schema,CN=Configuration,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.546]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.548]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Infrastructure,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.548]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.548]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=AD01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.548]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.555]
    Adprep discovered the schema FSMO: AD01.NJ01.IMSTRANSPORT.COM.
    [2012/12/27:16:27:25.559]
    Adprep connected to the schema FSMO: AD01.NJ01.IMSTRANSPORT.COM.
    [2012/12/27:16:27:25.559]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.559]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.559]
    Adprep successfully retrieved information from the Active Directory Domain Services.
    [2012/12/27:16:27:25.559]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.560]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/27:16:27:25.560]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.560]
    LDAP API ldap_search_ext_s finished, return code is 0x0 
    [2012/12/27:16:27:25.560]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.560]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/27:16:27:25.560]
    Adprep does not find the tokenGroups attribute on the RootDSE object of the Active Directory Domain Controller. This attribute is not avaliable on Windows Server 2003 or lower version of Windows. Adprep will try to obtain token groups from the User object.
    [2012/12/27:16:27:25.560]
    The parameters /userdomain and /user are not specified. Using current logon user's domain ...
    [2012/12/27:16:27:25.560]
    The current logon user's domain is NJ01.IMSTRANSPORT.COM.
    [2012/12/27:16:27:25.561]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.561]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.561]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.562]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.562]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Benjamin Green,OU=IT,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.563]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/27:16:27:25.569]
    Adprep discovered the Infrastructure FSMO: AD01.NJ01.IMSTRANSPORT.COM.
    [2012/12/27:16:27:25.572]
    Adprep connected to the Infrastructure FSMO: AD01.NJ01.IMSTRANSPORT.COM.
    [2012/12/27:16:27:25.572]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.572]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.572]
    Adprep successfully retrieved information from the Active Directory Domain Services.
    [2012/12/27:16:27:25.572]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.573]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/27:16:27:25.573]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.573]
    LDAP API ldap_search_ext_s finished, return code is 0x0 
    [2012/12/27:16:27:25.573]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.573]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/27:16:27:25.574]
    Adprep does not find the tokenGroups attribute on the RootDSE object of the Active Directory Domain Controller. This attribute is not avaliable on Windows Server 2003 or lower version of Windows. Adprep will try to obtain token groups from the User object.
    [2012/12/27:16:27:25.574]
    The parameters /userdomain and /user are not specified. Using current logon user's domain ...
    [2012/12/27:16:27:25.574]
    The current logon user's domain is NJ01.IMSTRANSPORT.COM.
    [2012/12/27:16:27:25.574]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.575]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.575]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.575]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.575]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Benjamin Green,OU=IT,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.576]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/27:16:27:25.591]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/27:16:27:25.592]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.592]
    Adprep successfully retrieved information from the Active Directory Domain Services.
    [2012/12/27:16:27:25.592]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=UID,CN=Schema,CN=Configuration,DC=NJ01,DC=IMSTRANSPORT,DC=COM.
    [2012/12/27:16:27:25.592]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/27:16:27:25.592]
    Adprep successfully determined whether Microsoft Windows Services for UNIX (SFU) is installed or not. If adprep detected SFU, adprep also verified that Microsoft hotfix Q293783 for SFU has been applied.
    [2012/12/27:16:27:25.611]
    Adprep could not retrieve data from the server AD01.NJ01.IMSTRANSPORT.COM through Windows Managment Instrumentation (WMI).
    [User Action]
    Check the log file ADPrep.log in the C:\Windows\debug\adprep\logs\20121227162725-test directory for possible cause of failure.
    [2012/12/27:16:27:25.611]
    Adprep encountered a Win32 error. 
    Error code: 0x5 Error message: Access is denied.
    DSID Info:
    DSID: 0x1810012a
    HRESULT = 0x80070005
    NT BUILD: 9200
    NT BUILD: 16384
    [2012/12/27:16:27:25.611]
    Adprep failed while performing Exchange schema check.
    [Status/Consequence]
    The Active Directory Domain Services schema is not upgraded.
    [User Action]
    Check the log file ADPrep.log in the C:\Windows\debug\adprep\logs\20121227162725-test directory for possible cause of failure.
    [2012/12/27:16:27:25.611]
    Adprep encountered a Win32 error. 
    Error code: 0x5 Error message: Access is denied.
    DSID Info:
    DSID: 0x1810012a
    HRESULT = 0x80070005
    NT BUILD: 9200
    NT BUILD: 16384

    Make sure that the server 2012 is already an member of the domain before upgrading it to an domain controller.
    To use an server 2012 domain in an 2003 envoirment you need to run adprep its located on the server 2012 disk ..\support\adprep
    When everything is looking fine your adprep will show you this.
    PS C:\Users\Administrator> D:\support\adprep\adprep.exe /forestprep
    ADPREP WARNING:
    Before running adprep, all Windows Active Directory Domain Controllers in the forest must run Windows Server 2003 or lat
    er.
    You are about to upgrade the schema for the Active Directory forest named 'domain', using the Active Directory
     domain controller (schema master) 'SRV2012SRV01.domain.local'.
    This operation cannot be reversed after it completes.
    [User Action]
    If all domain controllers in the forest run Windows Server 2003 or later and you want to upgrade the schema, confirm by
    typing 'C' and then press ENTER to continue. Otherwise, type any other key and press ENTER to quit.
    Then start server manager and click 'Add roles and features' and install the needed services.
    it did not work. here is the contents of the log. 
    [2012/12/28:09:44:36.122]
    Adprep created the log file 'C:\Windows\debug\adprep\logs\20121228094436\ADPrep.log'
    [2012/12/28:09:44:36.122]
    Adprep successfully initialized global variables.
    [Status/Consequence]
    Adprep is continuing.
    [2012/12/28:09:44:36.193]
    Adprep discovered the schema FSMO: <DC>.<DOMAIN NAME>.
    [2012/12/28:09:44:36.302]
    Adprep connected to the schema FSMO: <DOMAIN NAME>.
    [2012/12/28:09:44:36.302]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/28:09:44:36.303]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:36.303]
    Adprep successfully retrieved information from the Active Directory Domain Services.
    [2012/12/28:09:44:36.303]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=<DOMAIN>,DC=<DOMAIN>,DC=COM.
    [2012/12/28:09:44:36.303]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/28:09:44:36.303]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/28:09:44:36.303]
    LDAP API ldap_search_ext_s finished, return code is 0x0 
    [2012/12/28:09:44:36.303]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/28:09:44:36.304]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/28:09:44:36.304]
    Adprep does not find the tokenGroups attribute on the RootDSE object of the Active Directory Domain Controller. This attribute is not avaliable on Windows Server 2003 or lower version of Windows. Adprep will try to obtain token groups from the User object.
    [2012/12/28:09:44:36.304]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/28:09:44:36.305]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:36.305]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=<DOMAIN>,DC=<DOMAIN>,DC=COM.
    [2012/12/28:09:44:36.305]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:36.305]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is DC=<DOMAIN>,DC=<DOMAIN>,DC=COM.
    [2012/12/28:09:44:36.306]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/28:09:44:36.306]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=<NAME>,OU=<OU>,DC=<DOMAIN>,DC=<DOMAIN>,DC=COM.
    [2012/12/28:09:44:36.307]
    LDAP API ldap_search_s finished, return code is 0x0 
    [2012/12/28:09:44:36.346]
    Adprep successfully logged on to the local machine using the specified credentials for network connections.
    [2012/12/28:09:44:36.346]
    Adprep successfully made the network connection to the Active Directory Domain Controller <DC>.<DOMAIN>.<DOMAIN NAME>.COM.
    [2012/12/28:09:44:36.376]
    Adprep successfully stopped using the specified credentials for network connections.
    [2012/12/28:09:44:36.377]
    Adprep successfully closed the network connection to the Active Directory Domain Controller <DC>.<DOMAIN>.<DOMAIN NAME>.COM.
    [2012/12/28:09:44:36.380]
    Adprep discovered the schema FSMO: <DC>.<DOMAIN>.<DOMAIN NAME>.COM.
    [2012/12/28:09:44:36.384]
    Adprep connected to the schema FSMO: <DC>.<DOMAIN>.<DOMAIN NAME>.COM.
    [2012/12/28:09:44:36.386]
    Adprep successfully logged on to the local machine using the specified credentials for network connections.
    [2012/12/28:09:44:36.386]
    Adprep successfully made the network connection to the Active Directory Domain Controller <DC>.<DOMAIN>.<DOMAIN NAME>.COM.
    [2012/12/28:09:44:36.428]
    ADPREP WARNING: 
    Before running adprep, all Windows Active Directory Domain Controllers in the forest must run Windows Server 2003 or later.
    You are about to upgrade the schema for the Active Directory forest named '<DOMAIN>.<DOMAIN NAME>.COM.', using the Active Directory domain controller (schema master) '<DC>.<DOMAIN>.<DOMAIN NAME>.COM.'.
    This operation cannot be reversed after it completes.
    [User Action]
    If all domain controllers in the forest run Windows Server 2003 or later and you want to upgrade the schema, confirm by typing 'C' and then press ENTER to continue. Otherwise, type any other key and press ENTER to quit.
    [2012/12/28:09:44:40.475]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Schema,CN=Configuration,DC=<DOMAIN>,DC=<DOMAIN NAME>,DC=COM.
    [2012/12/28:09:44:40.475]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:40.475]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=<DC>,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=<DOMAIN>,DC=<DOMAIN NAME>,DC=COM.
    [2012/12/28:09:44:40.475]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:40.476]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=Schema,CN=Configuration,DC=<DOMAIN>,DC=<DOMAIN NAME>,DC=COM.
    [2012/12/28:09:44:40.476]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:40.476]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).
    [2012/12/28:09:44:40.477]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:40.477]
    Adprep successfully retrieved information from the Active Directory Domain Services.
    [2012/12/28:09:44:40.477]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is CN=UID,CN=Schema,CN=Configuration,DC=<DOMAIN>,DC=<DOMAIN NAME>,DC=COM.
    [2012/12/28:09:44:40.477]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2012/12/28:09:44:40.477]
    Adprep successfully determined whether Microsoft Windows Services for UNIX (SFU) is installed or not. If adprep detected SFU, adprep also verified that Microsoft hotfix Q293783 for SFU has been applied.
    [2012/12/28:09:44:40.512]
    Adprep could not retrieve data from the server <DC>.<DOMAIN>.<DOMAIN NAME>.COM through Windows Managment Instrumentation (WMI).
    [User Action]
    Check the log file ADPrep.log in the C:\Windows\debug\adprep\logs\20121228094436 directory for possible cause of failure.
    [2012/12/28:09:44:40.519]
    Adprep encountered a Win32 error. 
    Error code: 0x5 Error message: Access is denied.
    DSID Info:
    DSID: 0x1810012a
    HRESULT = 0x80070005
    NT BUILD: 9200
    NT BUILD: 16384
    [2012/12/28:09:44:40.541]
    Adprep failed while performing Exchange schema check.
    [Status/Consequence]
    The Active Directory Domain Services schema is not upgraded.
    [User Action]
    Check the log file ADPrep.log in the C:\Windows\debug\adprep\logs\20121228094436 directory for possible cause of failure.
    [2012/12/28:09:44:40.549]
    Adprep encountered a Win32 error. 
    Error code: 0x5 Error message: Access is denied.
    DSID Info:
    DSID: 0x1810012a
    HRESULT = 0x80070005
    NT BUILD: 9200
    NT BUILD: 16384
    [2012/12/28:09:44:40.549]
    Adprep successfully stopped using the specified credentials for network connections.
    [2012/12/28:09:44:40.550]
    Adprep successfully closed the network connection to the Active Directory Domain Controller <DC>.<DOMAIN>.<DOMAIN NAME>.COM.
    Looks like the problem is that
    Adprep could not retrieve data from the server <DC>.<DOMAIN>.<DOMAIN NAME>.COM through Windows Managment Instrumentation (WMI).
    how do i fix this so it will work??
    the other two domain controllers are running windows server 2003 32-bit operating systems.
    could the cause of this problem be that the server 2012 is 64-bit and the server 2003 machines are 32-bit???

  • New Server 2012 R2 Getting AD / SYSVOL Mismatch

    I just loaded up a fresh copy of Server 2012 R2 in VMWare and made it a Domain Controller.  To get a feeling of it before I deploy it.
    All the Windows updates have been done.
    Ran the Group Policy Results Wizard and got these alerts.
    Default Domain Controller Policy  Alert: AD / SYSVOL Version Mismatch
    Default Domain Policy  Alert: AD / SYSVOL Version Mismatch
    I found that there is a hot fix for this for Server 2012.
    http://support.microsoft.com/kb/2866345
    But when I run the hot fix it tells me that "The update is not applicable to your computer"
    So how do i fix this issue? Dont want to deploy Server 2012 R2 to my live enviorment only to have issues.

    Windows 8.1 and Windows Server 2012 R2 update information
    To resolve this issue in Windows 8.1 and Windows Server 2012 R2, install update rollup 2919394. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:
    2919394
          (http://support.microsoft.com/kb/2919394/            )    
    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: February 2014
    http://www.microsoft.com/en-us/download/details.aspx?id=41814 Update for Windows Server 2012 R2 (KB2919394)
    How to obtain the update
    Windows Update
    This update is provided as an Optional update from Windows Update. To obtain this update from Windows Update, follow these steps:
    Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click
    Search.
    In the search box, type Windows Update, and then tap or click
    Windows Update.
    Check online for updates, and then select the update for KB2919394 in optional updates.
    Microsoft Download Center
    You can also obtain the stand-alone update package through the Microsoft Download Center. For more information, go to the
    Microsoft Download Center
          (http://download.microsoft.com/)    
    , and then search for KB2919394.
    http://www.microsoft.com/en-us/download/details.aspx?id=41814
    Version:
    Date Published:
    2919394
    2/10/2014
    File name:
    File size:
    Windows8.1-KB2919394-x64.msu
    47.0 MB

  • New Server 2012 R2 virtual servers seem slow, how to tell if it's Windows or underlying VM host?

    We recently created two virtual Server 2012 R2 boxes, but the server seems rather pokey on a Remote Desktop session to it.  Task Manager doesn't show high processor usage (it reports 2.26GHz, 2 sockets, 4 virtual processors, virtual machine yes, L1
    cache N/A", memory is usually around 11%, and not a concerning amount of network traffic.
    Since both servers are pokey, I'm thinking that the issue may be in the VMware side, or the hard drives this is running off of are slow, or something not at the OS level.  But how can I confirm that, or at least say that without a doubt it has nothing
    to do with Windows?

    Hi RJO22,
    >>Task Manager doesn't show high processor usage (it reports 2.26GHz,
    2 sockets, 4 virtual processors,
    It seems that the VM spanned two NUMA nodes .
    Is there any other VM show the processor usage ( 1 socket ) ?
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.
    I looked at another virtual server we have, and it shows 2.226/2/4 just like that one.  Is that bad or does that cause performance issues with how mine say 2?

  • New WSUS on Server 2012 - problem with win8 clients

    Hi,
    Two weeks ago we created a new Server 2012 and installed the WSUS role from scratch on it.  Its version number is:  6.2.9200.16384.  It replaced a Server 2008 WSUS server.  After some time all the win7 clients updated and reported as
    they did on the old and replaced server.
    However all our win8 clients refuse to update against this server.  They show correctly up in WSUS server console each with 107 needed updates day after day.  We have rebooted them and done numerous wuauclt /resetauthorization /detectnow and wuauclt
    /detectnow /reportnow, but to no avail.
    I paste in some lines from a win8 client winupdate log at the end of this message if someone can figure out what I have to do to get these clients update as they did against the old wsus server.  Thanks for help on this issue.
    regards Tor
    2014-02-03    08:33:38:008     920    153c    Agent    *************
    2014-02-03    08:33:38:008     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:38:008     920    153c    Agent    *********
    2014-02-03    08:33:38:008     920    153c    Agent      * Online = Yes; Ignore download priority = No
    2014-02-03    08:33:38:008     920    153c    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
    or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-02-03    08:33:38:008     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:38:008     920    153c    Agent      * Search Scope = {Machine & All Users}
    2014-02-03    08:33:38:008     920    153c    Agent      * Caller SID for Applicability: S-1-5-18
    2014-02-03    08:33:38:008     920    153c    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2014-02-03    08:33:38:008     920    1990    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-02-03    08:33:38:008     920    1990    AU      # 0 updates detected
    2014-02-03    08:33:38:008     920    1990    AU    #########
    2014-02-03    08:33:38:008     920    1990    AU    ##  END  ##  AU: Search for updates  [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2014-02-03    08:33:38:008     920    1990    AU    #############
    2014-02-03    08:33:38:023     920    153c    Misc     Microsoft signed: Yes
    2014-02-03    08:33:38:023     920    153c    Misc     Infrastructure signed: Yes
    2014-02-03    08:33:38:023     920    153c    EP    Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab"
    2014-02-03    08:33:38:023     920    153c    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
    2014-02-03    08:33:38:039     920    153c    Misc     Microsoft signed: Yes
    2014-02-03    08:33:38:039     920    153c    Misc     Infrastructure signed: Yes
    2014-02-03    08:33:38:039     920    153c    EP    Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
    2014-02-03    08:33:38:055     920    153c    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-02-03    08:33:38:055     920    153c    PT      + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL = https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
    2014-02-03    08:33:38:055     920    153c    Agent    Reading cached app categories using lifetime 604800 seconds
    2014-02-03    08:33:38:055     920    153c    Agent    Read 0 cached app categories
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {E7FF661C-6A03-4387-A1EE-1D723B52EF60}.3 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:211     920    153c    Agent      * Found 13 updates and 31 categories in search; evaluated appl. rules of 69 out of 94 deployed entities
    2014-02-03    08:33:39:211     920    153c    Agent    *********
    2014-02-03    08:33:39:211     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:211     920    153c    Agent    *************
    2014-02-03    08:33:39:211     920    1a64    Report    REPORT EVENT: {0786C161-F6DC-4842-85D6-9506124654AD}    2014-02-03 08:33:38:008+0100    1  
     147 [AGENT_DETECTION_FINISHED]    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Update Command Line    Success    Software Synchronization  
     Windows Update Client successfully detected 0 updates.
    2014-02-03    08:33:39:211     920    1a64    Report    REPORT EVENT: {1E5D9728-220F-44A3-8BCC-ADE69687531D}    2014-02-03 08:33:38:008+0100    1  
     156 [AGENT_STATUS_30]    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Update Command Line    Success    Pre-Deployment Check  
     Reporting client status.
    2014-02-03    08:33:39:211     920    1a64    Report    REPORT EVENT: {57BAB7D0-685B-4D73-BDF7-82AFCE8675B0}    2014-02-03 08:33:39:211+0100    1  
     147 [AGENT_DETECTION_FINISHED]    101    {00000000-0000-0000-0000-000000000000}    0    0    Windows Update Command Line    Success    Software Synchronization  
     Windows Update Client successfully detected 13 updates.
    2014-02-03    08:33:39:211     920    1a64    Report    CWERReporter finishing event handling. (00000000)
    2014-02-03    08:33:39:227     920    153c    Agent    *************
    2014-02-03    08:33:39:227     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:227     920    153c    Agent    *********
    2014-02-03    08:33:39:227     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:227     920    153c    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
    or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-02-03    08:33:39:227     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:227     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:227     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1155
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:258     920    153c    Agent      * Found 11 updates and 29 categories in search; evaluated appl. rules of 58 out of 94 deployed entities
    2014-02-03    08:33:39:258     920    153c    Agent    *********
    2014-02-03    08:33:39:258     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:258     920    153c    Agent    *************
    2014-02-03    08:33:39:258     920    153c    Agent    *************
    2014-02-03    08:33:39:258     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:258     920    153c    Agent    *********
    2014-02-03    08:33:39:258     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:258     920    153c    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
    or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-02-03    08:33:39:258     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:258     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:258     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-2212025170-3189117132-1219651784-500
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:305     920    153c    Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
    2014-02-03    08:33:39:305     920    153c    Agent    *********
    2014-02-03    08:33:39:305     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:305     920    153c    Agent    *************
    2014-02-03    08:33:39:305     920    153c    Agent    *************
    2014-02-03    08:33:39:305     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:305     920    153c    Agent    *********
    2014-02-03    08:33:39:305     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:305     920    153c    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
    or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-02-03    08:33:39:305     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:305     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:305     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1323
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:352     920    153c    Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
    2014-02-03    08:33:39:352     920    153c    Agent    *********
    2014-02-03    08:33:39:352     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:352     920    153c    Agent    *************
    2014-02-03    08:33:39:352     920    153c    Agent    *************
    2014-02-03    08:33:39:352     920    153c    Agent    ** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:352     920    153c    Agent    *********
    2014-02-03    08:33:39:352     920    153c    Agent      * Online = No; Ignore download priority = No
    2014-02-03    08:33:39:352     920    153c    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
    or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-02-03    08:33:39:352     920    153c    Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-02-03    08:33:39:352     920    153c    Agent      * Search Scope = {Current User}
    2014-02-03    08:33:39:352     920    153c    Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1282
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
    2014-02-03    08:33:39:383     920    153c    Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
    2014-02-03    08:33:39:383     920    153c    Agent    *********
    2014-02-03    08:33:39:383     920    153c    Agent    **  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2014-02-03    08:33:39:383     920    153c    Agent    *************
    2014-02-03    08:33:39:383     920    1990    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-02-03    08:33:39:383     920    1990    AU      # 12 updates detected
    2014-02-03    08:33:39:383     920    1990    AU    #########
    2014-02-03    08:33:39:383     920    1990    AU    ##  END  ##  AU: Search for updates  [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-02-03    08:33:39:383     920    1990    AU    #############
    2014-02-03    08:33:39:383     920    1990    AU    All AU searches complete.
    2014-02-03    08:33:39:383     920    1990    AU    AU setting next detection timeout to 2014-02-03 10:18:51
    2014-02-03    08:33:44:211     920    1a64    Report    CWERReporter finishing event handling. (00000000)
    2014-02-03    08:41:39:472     920    1a64    EP    Got WSUS Client/Server URL: "http://elias:8530/ClientWebService/client.asmx"
    2014-02-03    08:41:39:472     920    1a64    PT    WARNING: Cached cookie has expired or new PID is available
    2014-02-03    08:41:39:472     920    1a64    EP    Got WSUS SimpleTargeting URL: "http://elias:8530"
    2014-02-03    08:41:39:472     920    1a64    PT    Initializing simple targeting cookie, clientId = c5e26849-287b-4b96-ba5d-1489d6fad2f2, target group = , DNS name = dt-ikt-tor.framnes.lan
    2014-02-03    08:41:39:472     920    1a64    PT      Server URL = http://elias:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-02-03    08:41:39:519     920    1a64    EP    Got WSUS Reporting URL: "http://elias:8530/ReportingWebService/ReportingWebService.asmx"
    2014-02-03    08:41:39:519     920    1a64    Report    Uploading 2 events using cached cookie, reporting URL = http://elias:8530/ReportingWebService/ReportingWebService.asmx
    2014-02-03    08:41:39:566     920    1a64    Report    Reporter successfully uploaded 2 events.
    2014-02-03    08:42:13:212     920    178c    Report    WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
    2014-02-03    08:43:40:450     920    178c    AU    ###########  AU: Uninitializing Automatic Updates  ###########
    2014-02-03    08:43:40:450     920    178c    WuTask    Uninit WU Task Manager
    2014-02-03    08:43:40:513     920    178c    Service    *********
    2014-02-03    08:43:40:513     920    178c    Service    **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-02-03    08:43:40:513     920    178c    Service    *************

    Today I opened Control Panel / Windows Updates and first did a check for new updates (from the WSUS server).  Nothing was found and it reported Windows is Updated.   Then I clicked the link Check for updates from Microsoft via internet, and
    it found around 24 updates.
    This is confirmation of the point that I made in the previous post. The updates are *NEEDED* by this system, but the updates were not *AVAILABLE* from the assigned WSUS Server. You were able to get them from Windows Update, but that does not fix your continuing
    issue with the WSUS Server.
    but it still reported the original 108 Needed updates.
    Exactly. As previously noted, the client is functioning perfectly. The problem is NOT with the client; the problem is with the WSUS Server. The updates that this client needed were not AVAILABLE to be downloaded from the WSUS server.
    Why this is the case requires further investigation on your part, but is either because the updates are not properly approved, or the update FILES are not yet downloaded from Microsoft to the WSUS server.
    It appears that the wsus server doesn't get any information back from the client despite that it displays new Last contact and Last Status report timestamps.
    This conclusion is incorrect. The WSUS Server got every bit of information available from the client -- you've confirmed this by the number of updates reported as "Needed" by the Windows Update Agent to the WSUS Server.
    I assumed that the log would display if the updates were downloaded or not.
    It will log when the updates are actually downloaded. If there's no log entries for updates being downloaded, then they're not being downloaded. If the logfile says "Found 0 updates", then that means exactly what it says: It couldn't find any approved/available
    updates to download.
    In your case it "Found 11 updates", but now it will be impossible to diagnose that fault, because you went and got them from Windows Update.
    All Win8 versions are checked in the WSUS server's Product list so the updates should at least have been downloaded to the server.
    This is why understanding the infrastructure is so critical. Your conclusion is invalid based on the premise given, and you may be using improper terminology which only confuses the rest of us as well.
    First, selecting updates for synchronization only gets the update metadata (i.e. the detection logic) downloaded to the WSUS database.
    The Second Step in this process is to Approve those updates for one or more WSUS Target Groups that contain the appropriate client systems. Following the approval of an update, the WSUS Server downloads the INSTALLATION FILE for that update.
    Once the WUAgent sees an approved update and the installation file is available, then the WUAgent will download the file and schedule the update for installation.
    Most of the post I read about my problem is about upgrading a 2008 WSUS server to support Win8 / Server 12 clients.  When I try to run this update on my Server 12 WSUS it refuses to run (probably because it is for Server 2008).
    Yeah.. totally different issue in those posts than what you're describing here.
    What should I do to try to track down the problem?
    Well.... now that it's 11 days since the logfile was posted, and you've already updated that system, we'll first need to find another system exhibiting the same issue.
    Then I'll need to ask a number of questions to properly understand the environment, as well as what you have or have not done.
    Then, from there, we can attempt to figure out why your Windows 8 client apparently sees some updates as approved/available but is still not downloading them. We do not yet have sufficient information to even speculate on a possible cause -- there are several.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Client installation is not successful & not showing activity in SCCM Server 2012

     Environment : SCCM Server 2012 Configured successfull and installed clients using client push method , successfully Completed . I have seen Active, And push software to corresponding clients . installed successfully
    We have internal & external networks in our environment . Internal network in data center , the sccm server is also in data center . All client systems is getting software's from sccm in internal network ( done successful) .
    i have opened the ports in firewall 135,139,80,443,445, etc (TCP,UDP)
    When iam trying to push the client from SCCM server to  external network client system. it is not installing the  Ccm setup ,
    not showing "Active" in SCCM server .
    I have added a Account in Client push , Same account i added in Client system Administrator group .
    Info : All systems in Device collection 
    please updated the suggestions, to solve this issue . 
    Thanks in advance 

    Client push requires more than just those handful of ports as it uses RPC and SMB to push the initial required files -- thus, you need to open the dynamic high ports required for RPC.
    You can easily see this activity in the ccm.log.If you are unable/unwilling to open the RPC high ports, then you should choose an alertnate client install method.
    Jason | http://blog.configmgrftw.com

  • Network Location not showing domain name in Server 2012 R2 after demoting 2003 PDC

    The single active NIC in my new Server 2012 R2 no longer shows the Network Location of "DOMAIN.LOCAL" like it did before I demoted the only Server 2003 domain controller. The NIC now shows "NETWORK" as the Network Location.
    The registry still shows a Profile with the correct PROFILENAME in
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
    but that name does not show up in the Network List Manager Policies inside Local Security Policy.
    The 2012 R2 Srv has all of the FSMO roles, Client PC's can connect to the domain but will not get new map drives from a script, they must be created manually. My Quickbooks Enterprise clients cannot see the QB Server Manager on this server and I think it
    is related to this issue because of firewall restrictions.
    The Windows Firewall pointed me in this direction because the "Private Networks" is connected to my NIC named "Network" but the Firewall "Domain Networks" is reported as "Not connected."
    Any Help is appreciated,
    CrazyDog

    Hi,
    Based on my research,
    Network Location Awareness (NLA) service expects to be able to enumerate the
    domain’s forest name to choose the right network profile for the connection. The service does this by calling
    DsGetDcName on the forest root name and issuing an LDAP query on UDP port 389 to a root Domain Controller.
    If something hinders the DNS name resolution or the connection attempt to the DC, NLA is not able to set the appropriate network profile on the connection.
    Therefore, I suggest you check the DNS settings on DCs and other domain-joined machines, which should point to the existing DC as preferred DNS server, and secondary DC as alternate DNS server, IP address of demoted DC should be
    removed. In addition, please do not use loopback IP address.
    Here are some articles below I suggest you refer to:
    Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles
    http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx
    Network Location Awareness
    http://technet.microsoft.com/en-us/library/cc753545(v=WS.10).aspx
    Complete Step by Step to Remove an Orphaned Domain controller
    http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx
    Best Regards.
    Amy

  • Serial Port communication very slow in RDP on windows server 2012

    Hellò, we have installed a new server 2012 and connected some thinclients via RDP, since that moment all peripherals connected to the imported com ports of the thinclients are running very slow, for example the cash register issue any receipt only after
    15-20 seconds!!. We have try to connect via RDP also a personal computer with many other OS like windows 8, windows 7, or XP but the result is the same: 15-20 seconds for a receipt!! We solve the problem only changing the server 2012 with a old server
    2008 or 2003!. How is possible window server 2012 is so slow on RDP imported com ports??. There is something to set for speed up the com ports on rdp? For us this is a great problem, all of our customers are using cash register via RDP and they can't wait
    all this time for a receipt. For your information we have tried to connect the cash register to the same com port of the same thinclient to the same server 2012 without RDP and the issue of the receipt is fast, so the problem is something on RDC of the new
    OS windows Server 2012. Also note this is a bi-directional communication because the cash register use a bi-directional communication for printing each one of the voice on the receipt, this problem wll not affect other printers unidirectional where the
    print process starting in less one second. Please help us to solve this problem, otherwise we will not more install windows server 2012.

    Hi,
    Thanks for your posting in Windows Server Forum.
    When the slow performance issue occurs on server 2012, check the Windows Logs – Application category of the Event Viewer (eventvwr.msc) on both the client and server sides. If there is any logs recorded, please let us know them. Please also check the
    driver is properly installed on server and check the compability guide with the cash register machine, whether it support server 2012 with remote session. If there is particular requirement then you need to solve them first.
    In addition, would like you to try connecting with RDP 8.1 and check whether it faces same issue.
    Remote Desktop Protocol 8.1 Update for Windows 7 SP1 released to web
    Hope it helps!
    Thanks,
    Dharmesh

Maybe you are looking for