Windows 2008 r2 Server: Cant update the group belonging

Hello,
I have a Windows 7 client computer which is administered by a Windows 2008 Server.
When I try to change the local grants of the user account in that client computer,  it appears to me the following message:
"Cant update the group belonging for NameDomain\user"
As result I cant change local grants for the user. I cant change his status from administrator to user of that machine.
Can anybody tell me how can I solve this issue?
Thanks in advance
Regards

Hi,
Thanks for your feedback. Did you mean that the issue exists after you removed
DameWare tools?
Please make sure that you have more than one administrator account on your computer, or you can't change it to a standard account since Windows requires at least one administrator account on a computer.
If you have another administrator account, you can try to use it to change the user’s account type.
Best regards,
Susie

Similar Messages

  • ACS 5.2 Sync with Windows 2008 AD but cannot see the Groups

    Hi Pals,
    Recently I've been working with the ACS 5.2 (Installed on VMWare). At the beginning I was using a Win Server 2003 Enterprise edition AD, and there was no problem with the AD and the CA Authority. Because some of my customers use Win Server 2008 I change the AD platform to Win Server 2008 Enterprise edition  (x64).
    I don't really have a great experience with Win Server Platforms and, for what I've seen, the Win Server 2003 Services deployment is easier than the Win Server 2008 is.
    So, when I used the Win server 2003 I could not only synchronize the ACS with the AD but also use some groups created on the AD to perform the Network Access Authentication. When I try to do the same with the Win Server 2008 AD the ACS and the Server get Synchronized but when I want to add the groups for the Authentication purposes there is no one, absolutely nothing... so I cannot do any test.
    Also I looked for information about the compatibility between the ACS 5.2 and the Win Server 2008 platforms and at the end the platforms are compatibles.
    Any Idea??
    Thanks in Advance.
    Jose M Cortes H

    Hi Jose,
    This should generally work.
    From what I could read, you cannot list AD groups when trying to select them under an authentication/authorization rule.
    What about when trying to list them under the AD configuration?
    Users and Identity Stores > External Identify Stores > Active Directory > Directory Groups > select...
    Unfortunately, without more details on a specific error message, it would be hard to tell where the root cause could lie.
    We could collect some initial logs from ACS 5.2, in order to start isolating the issue:
    1. Log in to the ACS command line and enable the following debugs:
    admin# acs-config
    Escape character is CNTL/D.
    Username:
    Password:
    acsadmin(config-acs)# debug-adclient enable
    acsadmin(config-acs)# debug-log mgmt level debug
    acsadmin(config-acs)# debug-log runtime level debug
    2. Recreate the issue a couple of times by trying to list the AD groups in the authentication rule and even by trying to list them under
    Users and Identity Stores > External Identify Stores > Active Directory > Directory Groups > select...
    3. Take note of the time stamp when you recreate the issue and then collect the ACS support bundle from the Monitoring & Report Viewer, under
    Troubleshooting > ACS Support Bundle
    Please be sure of collecting the support bundle while checking the following options:
    Include full configuration database = Unchecked
    Include debug logs = All
    Include local logs = All
    Include core files = All
    Include monitoring and reporting logs (all categories checked) = Include files from the last 1 day
    Also, please communicate the time stamp when the issue is observed, so that we can track it faster in the logs.
    Regards,
    Fede
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • Default OS performance counters processor, memory, logincal disk are missing in windows 2008 standard server

    I have a windows 2008 standard server in which the default OS performance counters counters processor, memory, logincal disk are missing.
    I tried using exctrlst.exe tool. This tool shows that the respective performance counters are already enabled but when I check in perfmon.msc, these counters are not visible.
    I also tried to rebuild the performance counters from the OS disk. but it did not worked. still the counters are missing.
    Because of these counters are missing, am unable to monitor the utilization of CPU, memory and disks.
    any suggestions, workaround, recommendations or solutions. it will be more helpful and highly appreciated !!!!.
    Regards,
    GK.
    GK

    Hi GK,
    According to your description, it seems that the issue was the same as the one described in the article below. If you are running Windows Server 2008 64-bit, you can check the KB below:
    http://support.microsoft.com/en-us/kb/2554336
    In addition, the articles below would also be helpful to you:
    How to manually rebuild Performance Counter Library values
    Missing Performance Counters
    Best regards,
    Susie
    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 Subscriber Support, contact [email protected]

  • Windows 2008 R2 Server not showing update history and not detecting new updates

    Hi Sirs,
    We have a Windows 2008 R2 server which is showing an empty windows update history, and is not detecting new updates from the WSUS server. It says that the windows is up to date, no error when trying to detect new updates, but I doubt it because when I checked
    the installed updates menu, it shows that that the most recent update date installed was last 2013, it just stop detecting and installing updates. I've already tried the ff workarounds but to no avail:
    1. restart wuauserv and bits service
    2. rename/delete the software distribution folder
    3. reinstalled the update agent/restarted the server
    4. deleted the susclientid on the registry
    Thanks in advanced for your help.
    here's the windowsupdate.log:
    2014-07-22    00:57:06:728     928    a34    AU    #############
    2014-07-22    00:57:06:728     928    a34    AU    Successfully wrote event for AU health state:0
    2014-07-22    00:57:06:728     928    a34    AU    Featured notifications is disabled.
    2014-07-22    00:57:06:728     928    a34    AU    AU setting next detection timeout to 2014-07-21 20:50:56
    2014-07-22    00:57:06:728     928    a34    AU    Successfully wrote event for AU health state:0
    2014-07-22    00:57:06:728     928    a34    AU    Successfully wrote event for AU health state:0
    2014-07-22    00:57:11:727     928    abc    Report    REPORT EVENT: {AF0753F1-F6F9-4583-87B0-A0B0AEA0C6A7}    2014-07-22 00:57:06:728+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    00:57:11:727     928    abc    Report    REPORT EVENT: {188957AA-577F-4DC5-9CDB-2D8CFEE96670}    2014-07-22 00:57:06:728+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    00:57:11:727     928    abc    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    01:11:10:931     928    abc    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    01:11:10:947     928    abc    Report    Reporter successfully uploaded 2 events.
    2014-07-22    04:50:56:736     928    1130    AU    #############
    2014-07-22    04:50:56:736     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    04:50:56:736     928    1130    AU    #########
    2014-07-22    04:50:56:736     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
    2014-07-22    04:50:56:736     928    d08    Agent    *************
    2014-07-22    04:50:56:736     928    d08    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    04:50:56:736     928    d08    Agent    *********
    2014-07-22    04:50:56:736     928    d08    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    04:50:56:736     928    d08    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-07-22    04:50:56:736     928    d08    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    04:50:56:736     928    d08    Agent      * Search Scope = {Machine}
    2014-07-22    04:50:57:017     928    d08    Setup    Checking for agent SelfUpdate
    2014-07-22    04:50:57:017     928    d08    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    04:50:57:017     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    04:50:57:017     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:611     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    04:50:59:611     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:611     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    04:50:59:611     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:626     928    d08    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    04:50:59:626     928    d08    Misc     Microsoft signed: Yes
    2014-07-22    04:50:59:626     928    d08    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    04:50:59:626     928    d08    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    04:50:59:626     928    d08    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    04:51:01:095     928    d08    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    04:51:01:095     928    d08    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    04:51:01:110     928    d08    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    04:51:01:110     928    d08    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    04:51:01:142     928    d08    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    04:51:01:142     928    d08    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    04:51:01:860     928    d08    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    04:51:01:860     928    d08    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    04:51:01:891     928    d08    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    04:51:01:891     928    d08    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    04:51:01:891     928    d08    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    04:51:04:485     928    d08    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    04:51:04:485     928    d08    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    04:51:04:875     928    d08    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    04:51:04:875     928    d08    Agent    *********
    2014-07-22    04:51:04:875     928    d08    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    04:51:04:875     928    d08    Agent    *************
    2014-07-22    04:51:04:875     928    1278    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
    2014-07-22    04:51:04:875     928    1278    AU      # 0 updates detected
    2014-07-22    04:51:04:875     928    1278    AU    #########
    2014-07-22    04:51:04:875     928    1278    AU    ##  END  ##  AU: Search for updates [CallId = {F40B494F-91F1-4FFB-B7A5-46CEA397AA52}]
    2014-07-22    04:51:04:875     928    1278    AU    #############
    2014-07-22    04:51:04:875     928    1278    AU    Successfully wrote event for AU health state:0
    2014-07-22    04:51:04:875     928    1278    AU    Featured notifications is disabled.
    2014-07-22    04:51:04:875     928    1278    AU    AU setting next detection timeout to 2014-07-22 00:38:28
    2014-07-22    04:51:04:875     928    1278    AU    Successfully wrote event for AU health state:0
    2014-07-22    04:51:04:875     928    1278    AU    Successfully wrote event for AU health state:0
    2014-07-22    04:51:09:874     928    d08    Report    REPORT EVENT: {FE398C01-75A1-4AD8-8C43-0894FCFCE13F}    2014-07-22 04:51:04:875+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    04:51:09:874     928    d08    Report    REPORT EVENT: {CDA386AD-6392-4C34-859E-35307BCB5EA0}    2014-07-22 04:51:04:875+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    04:51:09:874     928    d08    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    05:05:09:109     928    d08    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    05:05:09:109     928    d08    Report    Reporter successfully uploaded 2 events.
    2014-07-22    08:38:28:883     928    1130    AU    #############
    2014-07-22    08:38:28:883     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    08:38:28:883     928    1130    AU    #########
    2014-07-22    08:38:28:883     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
    2014-07-22    08:38:28:883     928    53c    Agent    *************
    2014-07-22    08:38:28:883     928    53c    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    08:38:28:883     928    53c    Agent    *********
    2014-07-22    08:38:28:883     928    53c    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    08:38:28:883     928    53c    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-07-22    08:38:28:883     928    53c    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    08:38:28:883     928    53c    Agent      * Search Scope = {Machine}
    2014-07-22    08:38:29:195     928    53c    Setup    Checking for agent SelfUpdate
    2014-07-22    08:38:29:195     928    53c    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    08:38:29:195     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    08:38:29:195     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:804     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    08:38:31:804     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:804     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    08:38:31:820     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:820     928    53c    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    08:38:31:820     928    53c    Misc     Microsoft signed: Yes
    2014-07-22    08:38:31:835     928    53c    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    08:38:31:835     928    53c    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    08:38:31:835     928    53c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    08:38:33:241     928    53c    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    08:38:33:241     928    53c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    08:38:33:272     928    53c    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    08:38:33:272     928    53c    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    08:38:33:288     928    53c    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    08:38:33:288     928    53c    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    08:38:33:991     928    53c    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    08:38:33:991     928    53c    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    08:38:34:038     928    53c    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    08:38:34:038     928    53c    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    08:38:34:038     928    53c    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    08:38:36:616     928    53c    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    08:38:36:616     928    53c    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    08:38:37:022     928    53c    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    08:38:37:022     928    53c    Agent    *********
    2014-07-22    08:38:37:022     928    53c    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    08:38:37:022     928    53c    Agent    *************
    2014-07-22    08:38:37:022     928    aa8    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
    2014-07-22    08:38:37:022     928    aa8    AU      # 0 updates detected
    2014-07-22    08:38:37:022     928    aa8    AU    #########
    2014-07-22    08:38:37:022     928    aa8    AU    ##  END  ##  AU: Search for updates [CallId = {9A097F9F-88DD-4037-A4DD-48B9CC891327}]
    2014-07-22    08:38:37:022     928    aa8    AU    #############
    2014-07-22    08:38:37:022     928    aa8    AU    Successfully wrote event for AU health state:0
    2014-07-22    08:38:37:022     928    aa8    AU    Featured notifications is disabled.
    2014-07-22    08:38:37:022     928    aa8    AU    AU setting next detection timeout to 2014-07-22 04:15:53
    2014-07-22    08:38:37:022     928    aa8    AU    Successfully wrote event for AU health state:0
    2014-07-22    08:38:37:022     928    aa8    AU    Successfully wrote event for AU health state:0
    2014-07-22    08:38:42:021     928    53c    Report    REPORT EVENT: {45B5AD35-C612-4C43-8FE0-DFC63B114FC9}    2014-07-22 08:38:37:022+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    08:38:42:021     928    53c    Report    REPORT EVENT: {BA606714-0153-41BA-ADC8-78520F678D97}    2014-07-22 08:38:37:022+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    08:38:42:021     928    53c    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    08:52:41:224     928    53c    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    08:52:41:240     928    53c    Report    Reporter successfully uploaded 2 events.
    2014-07-22    12:15:53:027     928    1130    AU    #############
    2014-07-22    12:15:53:027     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    12:15:53:027     928    1130    AU    #########
    2014-07-22    12:15:53:027     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
    2014-07-22    12:15:53:043     928    a58    Agent    *************
    2014-07-22    12:15:53:043     928    a58    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    12:15:53:043     928    a58    Agent    *********
    2014-07-22    12:15:53:043     928    a58    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    12:15:53:043     928    a58    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-07-22    12:15:53:043     928    a58    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    12:15:53:043     928    a58    Agent      * Search Scope = {Machine}
    2014-07-22    12:15:53:308     928    a58    Setup    Checking for agent SelfUpdate
    2014-07-22    12:15:53:308     928    a58    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    12:15:53:308     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    12:15:53:324     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:901     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    12:15:55:901     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:901     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    12:15:55:917     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:917     928    a58    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    12:15:55:917     928    a58    Misc     Microsoft signed: Yes
    2014-07-22    12:15:55:933     928    a58    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    12:15:55:933     928    a58    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    12:15:55:933     928    a58    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    12:15:57:167     928    a58    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    12:15:57:167     928    a58    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    12:15:57:167     928    a58    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    12:15:57:167     928    a58    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    12:15:57:198     928    a58    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    12:15:57:198     928    a58    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    12:15:57:917     928    a58    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    12:15:57:917     928    a58    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    12:15:57:963     928    a58    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    12:15:57:963     928    a58    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    12:15:57:963     928    a58    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    12:16:00:572     928    a58    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    12:16:00:572     928    a58    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    12:16:00:932     928    a58    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    12:16:00:932     928    a58    Agent    *********
    2014-07-22    12:16:00:932     928    a58    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    12:16:00:932     928    a58    Agent    *************
    2014-07-22    12:16:00:932     928    1120    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
    2014-07-22    12:16:00:932     928    1120    AU      # 0 updates detected
    2014-07-22    12:16:00:932     928    1120    AU    #########
    2014-07-22    12:16:00:932     928    1120    AU    ##  END  ##  AU: Search for updates [CallId = {9BDC1D71-5139-49D4-88F0-E2B639CE8846}]
    2014-07-22    12:16:00:932     928    1120    AU    #############
    2014-07-22    12:16:00:932     928    1120    AU    Successfully wrote event for AU health state:0
    2014-07-22    12:16:00:932     928    1120    AU    Featured notifications is disabled.
    2014-07-22    12:16:00:932     928    1120    AU    AU setting next detection timeout to 2014-07-22 08:15:22
    2014-07-22    12:16:00:932     928    1120    AU    Successfully wrote event for AU health state:0
    2014-07-22    12:16:00:932     928    1120    AU    Successfully wrote event for AU health state:0
    2014-07-22    12:16:05:931     928    a58    Report    REPORT EVENT: {25E75367-1205-4F59-A812-02DA28BB3234}    2014-07-22 12:16:00:932+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    12:16:05:931     928    a58    Report    REPORT EVENT: {FE1434F8-C6AF-4F87-B3DF-6E4D6C4B05FB}    2014-07-22 12:16:00:932+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    12:16:05:931     928    a58    Report    CWERReporter finishing event handling. (00000000)
    2014-07-22    12:30:05:116     928    a58    Report    Uploading 2 events using cached cookie, reporting URL = http://mtp-wsus2/ReportingWebService/ReportingWebService.asmx
    2014-07-22    12:30:05:131     928    a58    Report    Reporter successfully uploaded 2 events.
    2014-07-22    14:05:29:584     928    10a0    AU    Triggering AU detection through DetectNow API
    2014-07-22    14:05:29:584     928    10a0    AU    Triggering Online detection (interactive)
    2014-07-22    14:05:29:584     928    1130    AU    #############
    2014-07-22    14:05:29:584     928    1130    AU    ## START ##  AU: Search for updates
    2014-07-22    14:05:29:584     928    1130    AU    #########
    2014-07-22    14:05:29:584     928    1130    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
    2014-07-22    14:05:29:584     928    8e0    Agent    *************
    2014-07-22    14:05:29:584     928    8e0    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    14:05:29:584     928    8e0    Agent    *********
    2014-07-22    14:05:29:584     928    8e0    Agent      * Online = Yes; Ignore download priority = No
    2014-07-22    14:05:29:584     928    8e0    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-07-22    14:05:29:584     928    8e0    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-22    14:05:29:584     928    8e0    Agent      * Search Scope = {Machine}
    2014-07-22    14:05:29:584     928    8e0    Setup    Checking for agent SelfUpdate
    2014-07-22    14:05:29:584     928    8e0    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-07-22    14:05:29:584     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    14:05:29:600     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:616     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-07-22    14:05:29:631     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:631     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    14:05:29:631     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:647     928    8e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-07-22    14:05:29:662     928    8e0    Misc     Microsoft signed: Yes
    2014-07-22    14:05:29:662     928    8e0    Setup    Determining whether a new setup handler needs to be downloaded
    2014-07-22    14:05:29:662     928    8e0    Setup    SelfUpdate handler is not found.  It will be downloaded
    2014-07-22    14:05:29:662     928    8e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    14:05:29:662     928    8e0    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    14:05:29:662     928    8e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    14:05:29:694     928    8e0    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    14:05:29:694     928    8e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2014-07-22    14:05:29:709     928    8e0    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2014-07-22    14:05:29:725     928    8e0    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-07-22    14:05:30:037     928    8e0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-07-22    14:05:30:037     928    8e0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    14:05:30:053     928    8e0    PT    WARNING: Cached cookie has expired or new PID is available
    2014-07-22    14:05:30:053     928    8e0    PT    Initializing simple targeting cookie, clientId = 487b95fe-31a4-44f7-9989-bd77766ce5fa, target group = , DNS name = itg-soatrainsvr.mbtc.mgc.local
    2014-07-22    14:05:30:053     928    8e0    PT      Server URL = http://mtp-wsus2/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-22    14:05:35:630     928    8e0    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-07-22    14:05:35:630     928    8e0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://mtp-wsus2/ClientWebService/client.asmx
    2014-07-22    14:05:36:411     928    8e0    Agent      * Found 0 updates and 68 categories in search; evaluated appl. rules of 503 out of 777 deployed entities
    2014-07-22    14:05:36:411     928    8e0    Agent    *********
    2014-07-22    14:05:36:411     928    8e0    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-07-22    14:05:36:411     928    8e0    Agent    *************
    2014-07-22    14:05:36:411     928    1360    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
    2014-07-22    14:05:36:411     928    1360    AU      # 0 updates detected
    2014-07-22    14:05:36:411     928    1360    AU    #########
    2014-07-22    14:05:36:411     928    1360    AU    ##  END  ##  AU: Search for updates [CallId = {CC67CC44-7DFB-49DE-AA83-8D6A7995ABFA}]
    2014-07-22    14:05:36:411     928    1360    AU    #############
    2014-07-22    14:05:36:411     928    1360    AU    Successfully wrote event for AU health state:0
    2014-07-22    14:05:36:411     928    1360    AU    Featured notifications is disabled.
    2014-07-22    14:05:36:411     928    1360    AU    AU setting next detection timeout to 2014-07-22 10:01:01
    2014-07-22    14:05:36:411     928    1360    AU    Successfully wrote event for AU health state:0
    2014-07-22    14:05:36:411     928    1360    AU    Successfully wrote event for AU health state:0
    2014-07-22    14:05:41:410     928    8e0    Report    REPORT EVENT: {6A2B180E-A95F-42F7-B775-5750DFFD6ECD}    2014-07-22 14:05:36:411+0800    1  
     147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows
    Update Client successfully detected 0 updates.
    2014-07-22    14:05:41:410     928    8e0    Report    REPORT EVENT: {83041427-693D-4A42-AED0-E8E7BFB8E7E3}    2014-07-22 14:05:36:411+0800    1  
     156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting
    client status.
    2014-07-22    14:05:41:410     928    8e0    Report    CWERReporter finishing event handling. (00000000)

    No Service Pack 1 installed. Does this mean that no updates will be detected if SP1 is not installed? thanks
    That's exactly what that means!
    Updates have not been available for Windows Server 2008 R2 *RTM* systems since April, 2013.
    http://support.microsoft.com/lifecycle/?p1=14134
    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.

  • Windows 2008 R2 Server without Service Pack 1 was flag "Not Required" during the SCCM patching/deploying SP1 for 2008

    Dear Brothers,
    I come to a scenario were one of our Windows 2008 R2 Server without Service Pack 1, was Flag under SCCM 2007 Reports Update Status for Service Pack 1 deployment to be "Not
    Required" which definitely inaccurate.
    What I want to know what are the conditions for the Software Update to send a status to SCCM Server that the Service Pack is “Not
    Required” instead of the other way around?
    Is there anyone that can guide me to any KB Article regarding this behavior?
    Regards,

    Yes, I know this is an old post, I’m trying to clean them up. Did you figure this out, if so how?
    I have seen this before and what I have done is manually applied the SP1 to the server. Only then did the error show up as why SP1 didn’t apply. After fixing the error, CM was apply to apply SP1 and other SU to the server.
    http://www.enhansoft.com/

  • Windows 2008 R2 Client computer backup files (*.dat) can't get restored after re-imaging the Windows 2008 R2 server

    I have a Windows server 2008 R2 and I'm using backup feature to backup all computers in the network on it. Recently I ran into an issue and had to re-image my Windows 2008 R2 server  and had to restore 2 of my client computers but now I can't restore
    files from my client computer backups because they are not listed under Backups & Devices anymore however all backup files are still available on my Backup drive. How can I retrieve files from these backup files?

    Anyone out there to help me with this issue?

  • When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

    When I try to print using Windows 2008 print server I have to use the generic print drivers supplied. If I use the OEM driver the printer locks up. I have tried a HP 4 plus and a Canon Copier.

    A number of vendor drivers written for OS X cannot be used when connecting via SMB to a printer that is shared by Windows. This is due to limitations of the driver.
    In some cases, if you were to enable the LPD Print Service in Windows, you can connect to the share using the same syntax as SMB but on the Mac you would use the LPD as the protocol.
    If you can reply with the brand and model of printer you have then we may be able to provide more information.

  • KMS Error 0xC004F015 on Windows 2008 R2 - Does anyone have the correct fix for this please?

    I am in the process of migrating my KMS server from Windows 2003 to Windows 2008 R2 64-bit. My Windows 2003 server has been happily providing my Windows 7 clients with licenses for well over a year. I have followed these migration steps in this forum article:
    social.technet.microsoft.com/Forums/windows/en-US/cd4177bd-8df5-4a66-afdc-c760398b7e7f/migrating-kms-server-from-one-computer-to-another?forum=itprovistaactivation
    I cannot get passed step 5. As soon as I try step 5 with my Windows 7 KMS key I receive error 0xC004F015. Despite reading countless articles on Microsoft forums and also speaking the Microsoft licensing who frankly were of no help at all, I am none the wiser
    how to resolve this fault. My questions are:
    1. Should my Windows 2008 R2 server be licensed with a MAK or KMS key? Does this matter?
    2. Some articles I have read suggest if you use a Windows Server "C" license then you do not need to use a Windows 7 KMS key. I've tried this but it just tells me I have insufficient licenses.
    3. When installing my windows 7 license key via the slmgr /ipk command should I be using my Windows 7 Professional KMS key? This works fine on my old Windows 2003 server, but Windows 2008 does not like it at all. Would I be better simply moving my KMS server
    to a Windows 7 desktop instead?
    4. I also want my Windows 2008 R2 to carry out my KMS activation for Office 2013. Can this run on the same server as my Windows 7 KMS key should I ever get it to work
    Thank you anyone who can shed some light on this absolutely baffling error. Surely some one out there has the definitive answer.
    Regards
    N Buck

    I am in the process of migrating my KMS server from Windows 2003 to Windows 2008 R2 64-bit. My Windows 2003 server has been happily providing my Windows 7 clients with licenses for well over a year. I have followed these migration steps in this
    forum article:
    social.technet.microsoft.com/Forums/windows/en-US/cd4177bd-8df5-4a66-afdc-c760398b7e7f/migrating-kms-server-from-one-computer-to-another?forum=itprovistaactivation
    I cannot get passed step 5. As soon as I try step 5 with my Windows 7 KMS key I receive error 0xC004F015. Despite reading countless articles on Microsoft forums and also speaking the Microsoft licensing who frankly were of no help at all, I am none the wiser
    how to resolve this fault. My questions are:
    1. Should my Windows 2008 R2 server be licensed with a MAK or KMS key? Does this matter?
    2. Some articles I have read suggest if you use a Windows Server "C" license then you do not need to use a Windows 7 KMS key. I've tried this but it just tells me I have insufficient licenses.
    3. When installing my windows 7 license key via the slmgr /ipk command should I be using my Windows 7 Professional KMS key? This works fine on my old Windows 2003 server, but Windows 2008 does not like it at all. Would I be better simply moving my KMS server
    to a Windows 7 desktop instead?
    4. I also want my Windows 2008 R2 to carry out my KMS activation for Office 2013. Can this run on the same server as my Windows 7 KMS key should I ever get it to work
    Hi,
    on your KMShost, if that is a WindowsServer OS, you cannot use a WindowsClient (WinVista/Win7/Win8/Win8.1) KMShost product key, you must use a WindowsServer KMShost product key.
    Further, the KMShost product key must match the OS of the KMShost machine (or exceed/better it).
    e.g. if your KMShost machine is WS2008R2, you must use a WS2008R2 (or higher e.g. WS2012 or WS2012R2) product key.
    If you will use a higher product key, you will need to install the relevant patch package to do so.
    When you install a Windows KMShost product key onto a machine, the Windows KMShost product key completely replaces the previous Windows product key of that machine [it serves two purposes, (1) replace the previous key, (2) activates the KMShost feature].
    So, your KMShost is neither licensed as MAK nor KMS, it becomes a KMShost.
    For WS2008R2 KMShosts, you can install one of 3 types (channels/groups) of KMshost pkey.
    The channel/group pkey you choose, is based upon the maximum product editions you wish to perform KMSclient activations for.
    http://technet.microsoft.com/en-us/library/ff793411.aspx
    For your issue #2, are you attempting to install your Windows7 KMS key upon the KMShost or a KMSclient?
    For your issue #3, are you attempting this upon a KMSclient? (Volume License editions on Win7Pro or Win7Ent, are already pre-loaded with a KMSclient pkey, so you should have no need to alter the client keys). As previously mentioned, no Win7 key is needed/possible
    for the KMShost, if the KMShost is WS2008R2.
    For your issue #4, yes, your WS2008R2 KMShost can also act as KMShost for Office2010 and/or Office2013, this requires a further patch, and the installation of the relevant Office KMShost pkey.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Does WCS run on Windows 2008 R2 server?

    Can anybody share his/her experience with running WCS on Windows 2008 R2 server?
    Is it possible and did you experience any problems with it? (during installation or during normal usage)
    Is it supported by Cisco already?
    Our distributor is a little bit vague about that, that's is why I am asking it here.

    From WCS 7 release notes :
    Operating Systems Requirements
    The following operating systems are supported:
    •Windows 2003/SP2 and Windows 2003 R2/SP2 32-bit installations with all critical and security Windows updates installed.
    Windows 2003/SP2 64-bit installations are not supported. A 32-bit  operating system running on a 64-bit capable hardware is supported.
    Windows 2003 32-bit installations provide support for up to 64 GB of RAM  if Physical Address Extension (PAE) is enabled. See the Windows  documentation for instructions on enabling this mode.
    •Red Hat Linux Enterprise Server 5.X 32-bit operating system installations.
    Red Hat Linux Enterprise Server 5.X 64-bit operating system  installations are not supported. A 32-bit operating system running on a  64-bit capable hardware is supported.
    •Windows  2003 and Red Hat Linux version support on VMware ESX version 3.0.1 and  above with either local storage or SAN over fiber channel.
    Individual operating systems running WCS in VMware must follow the specifications for the size of WCS that you intend to use.
    No Windows 2008 ! I know lots of people have been crying for it and it should be coming in next releases but no promises as of now :-(
    Nicolas

  • Moving SAP Content Server/MaxDB 7.6 to a Windows 2008 R2 Server

    Hi All.
    We are in the process of upgrading our server where the SAP content server is located.  We are going from SAP CS 6.30/MaxDB 7.6 to a Windows 2008 R2 server where we want to install SAP CS 6.40/MaxDB 7.8.  I have been following the latest manual from SAP for upgrading to MaxDb 7.8  (2010-10-05) from MaxDb 7.6 using the in-place method.
    To date we have installed MaxDB 7.6 on the server.  We restored our latest backup and performed the index checks as spelled out in the manual.  I have the database in ADMIN mode and went to run the MaxDb 7.8 install for the 64 bit window version.  THe install GUI comes up, but the Update selection is grayed out.  This tells me that the install program can not detect our existing database.  I did make sure I was running the install as Admim so I do not think that is the issue.
    This is the second time I have tried this upgrade.  The first time I did a comand line upgrade by runing the .bat file DBUPDATE.bat. We have a 110 Gbyte database and this upgrade ran in about 15 minutes, and of course when I went to openthe database it was toast.  Do not want to make the same mistake again.
    One other point, since we did a restore of the database, then the index check, we did not run a backup as the manual suggested as we felt it was not necessary.  Does the system require a backup before upgrade and that is why it does not see the database?
    Any assistance will be greatly appreciated.

    I beleive we have resolved the issue with upgrading the database, but now we are having a problem with Datbase Studio 7.8.  Before the upgrade we used Data Manager 7.6.  After the upgrade we installed Database Studio 7.8 and when we go to start it up, we are getting the Problems opening perspective 'com.sap.sdb.tools.ut.perspectives.mainPerspective'. I followed the instruction in another post Problems opening perspective in Database Studio, but we still are getting the error.
    Can anybody offer any assistance as we are getting close to the weekend when we want to do the cutover and we are not even done with our first pass at upgrading the SAP content server.
    Thanks
    John

  • Add Windows 2008 Terminal Server to RWW/RWA

    I would like to add our Windows 2008 Terminal Server (not R2) to RWW in Windows 2012R2 Essentials.  The connect computer wizard did not work on the Windows 2008 server, returning Win32 error.  
    How do I add the 2008 TS to the devices listing in RWW without using the connector wizard (as it does not work).   The Windows 2008 server has been join to the same domain manually.

    You cant add it as a tile device in the way you could in SBS 2011 Standard.
    You can create an RDP file, and save that so it is accessible via the RWA then add a link to the RWA to that file.
    You may need to tweak IIS to allow .rdp files.
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • Cannot TYPE in Windows 2008 remotre server.

    I cannot TYPE in Windows 2008 remotre server.
    I can open, close, save and ctrl+alt+delete to open the task manager, but that's it because I cannot type.
    When I close the remote connection everything else works just fine.

    Hi Amanda,
    In addition, you can also try to update RDP edition and NIC driver on problematic machines to see if it works.
    Best Regards,
    Amy

  • System.Windows.Forms.SaveFileDialog not working under Windows 2008 R2 Server

    I am using Windows Server 2008 R2 (64-bit) that is been virtualized with Hyper-V and it is being used as a "Remote Desktop Server".
    I am trying to use this PowerShell code that will open a "Save-File-Dialog" box to select the PDF file and send it to my "batch" file for scanning.  This code works great on my Windows Vista machine and my Windows 7 32-bit machine
    but I cannot get it to work on the "Windows 2008 R2 Server (64-bit)".  It will not come up with any window at all and it will not produce any errors at all, so I can't exactly google for this issue.  I am using PowerShell 2.0 from 2009.
    Any ideas?  I tried it from an Admin account and a regular domain users and neither worked at all, no errors, no window, no nothing.
    *** Update ***
        I took Out-Null out and I received this...
      GAC    Version        Location
    True   v2.0.50727     C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll
    I then checked the path and the DLL file was in there and it had read and execute permissions for Domain users and Administrators and the window still won't pop up... 
    Here is the entire code in question.....
    # Uses the dot net assembly to give the users a Save-File-Dialog box so they can decide where to put the pdf file
    Function Get-SaveFile($initialDirectory){
    [System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms") | Out-Null
    $SaveFileDialog = New-Object System.Windows.Forms.SaveFileDialog
    $SaveFileDialog.initialDirectory = $initialDirectory
    $SaveFileDialog.filter = "PDF files (*.pdf)| *.pdf"
    $SaveFileDialog.ShowDialog() | Out-Null
    $SaveFileDialog.filename
    # open dialog box to select the .nessuss file.
    $OutputFile = Get-SaveFile
    # User selected where they want to put the scanned.pdf file and it will automatically set it to .pdf for them
    start-process Scan $OutputFile

    I ran the code you have in your function on a Windows 2008 Standard server, and it seems to be hanging on the line
    $SaveFileDialog.ShowDialog()
    | Out-Null
    It just sits there and nothing happens, but if I run it on my Windows 7 machines, it runs without any issues. So it seems like the dialog opened, but behind the scenes, and is waiting on the user, but since it doesn't open, the user can't do anything.
    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
    Don't Retire Technet

  • Remote Access to Windows 2008 R2 Server configured with local IP

    Hello,
    I have a Windows 2008 R2 Server configured with local IP (e.g. 192.168.1.115).
    Please how can I access it remotely outside its local domain through (remote desktop connection).
    Thank you.
    Tony.

    Hi Tony,
    Based on your description, you would like to connect to the Windows 2008 R2 server via remote desktop connection.
    So you need to enable remote desktop on the Windows 2008 R2 server if it is not already.
    1.Install and configure the Remote Desktop Session Host role service in the Windows 2008 R2 server.
    2.Add related user to the Remote Desktop Users group in the Windows 2008 R2 server.
    3.Configure remote desktop connection in the Client.                   
    Also, due to you would like to access it remotely outside the domain, so you will need a VPN connection or a port forward to connect through.
    For more details, please refer to the guide below,
    Installing and Configuring Remote Desktop Session Host
    http://technet.microsoft.com/en-us/library/dd883253.aspx
    Allow Remote Desktop connections from outside your home network
    http://windows.microsoft.com/en-IN/windows7/allow-remote-desktop-connections-from-outside-your-home-network
    Best Regards,
    Tina

  • Need assistance with Windows 2008 R2 server BSOD - ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)

    Need assistance with Windows 2008 R2 server BSOD - ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    I have a Windows 2008 R2 server which is experiencing random BSOD during the night. This is occurring maybe once or twice a week. I have gathered two Memory crash files. This server is running Citrix XenApp 6.5 but nothing else is reporting an issue except
    for the memory dump. I’m looking for assistance in reading crash file and finding the cause.
    I’ve spent over a week going through articles trying to learn and trouble shoot the BSOD but no closer to understanding the WinDbg 6.3.9600 report.
    This is a production server and I have verified that Windows Updates has updated the server with latest releases. I’m hoping that the crash file will show something before I have to run the Driver Verifier.
    The crash zip file is located -
    https://onedrive.live.com/redir?resid=9644A4E0A26873B1!2359&authkey=!AMS4Svuk-SS3-JA&ithint=file%2czip
    *                        Bugcheck Analysis                                   
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory.  The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff880009eff38, Virtual address for the attempted execute.
    Arg2: 8000000002cfe963, PTE contents.
    Arg3: fffff8800da2eea0, (reserved)
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xFC
    PROCESS_NAME:  powershell.exe
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    TRAP_FRAME:  fffff8800da2eea0 -- (.trap 0xfffff8800da2eea0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa80070f3648 rbx=0000000000000000 rcx=fffffa80070f3648
    rdx=fffff8800da2fbf8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80001680b80 rsp=fffff8800da2f030 rbp=fffff8800da2fbd0
     r8=fffff8a01804c680  r9=fffff8800da2fc68 r10=fffffffffffffffd
    r11=fffff8800da2fa90 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na pe nc
    nt!KiPageFault:
    fffff800`01680b80 55              push    rbp
    Resetting default scope
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+44dfc
    fffff800`017008b8 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+44dfc
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb
    IMAGE_VERSION:  6.1.7601.18409
    FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
    BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+44dfc
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0xfc_nt!_??_::fnodobfm::_string_+44dfc
    FAILURE_ID_HASH:  {aa632d36-b0f7-67cf-89e2-1cec389c0a11}
    Followup: MachineOwner

    Hi Kaysel_GTG,
    Just addition. Regarding to Bug Check 0xFC, please refer to following article and check if can help you.
    Bug Check 0xFC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
    By the way, since it is not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer
    Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
    To obtain the phone numbers for specific technology request, please refer to the web site listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
    if any update, please feel free to let us know.
    Hope this helps.
    Best regards,
    Justin Gu

Maybe you are looking for