Edward

My feedback

  1. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Edward commented  · 

    In Build 1.1.1903.26001, when these steps are followed, it actually creates a Server Type with the same machine name as my Windows PC Type machine. It shows "Updates" and other items like "Roles and Features" but these obviously do not work because this is a PC object Type, not a Server. I have to then Delete the Server Type object. I'm not sure why it creates another object when looking at "Local Users and Groups" under settings.

    Edward supported this idea  · 
  2. 34 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Edward commented  · 

    While I can change the account that is utilized in WAC for that specific "session", I would really like that to be something that could be configured to stay. I have servers across domains that I need to utilize different accounts to manage via WAC and this changes every time back to the default when I close the session. I have some servers that are even not domain joined and that is reset to a "domain" account when the session ends. I would love to see the ability to manage with different accounts and the account name stay when the "Manage As" is edited. This would help in Azure as well since many of those are not "domain joined" either. Thanks!

    Edward supported this idea  · 
  3. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Edward supported this idea  · 
  4. 26 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Edward supported this idea  · 
  5. 40 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Edward supported this idea  · 
  6. 13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    Edward commented  · 

    I was an avid user of Windows Home Server, when it was deprecated, Windows Server Essentials was used to replace it. Now that I'm using Windows Server Essentials 2016, I too, would like to install this on my server to then manage my clients. But was frustrated to see that it cannot be installed on a domain controller. While I understand some of the ramifications, there are some who want to learn and use this in their very small environment. Installing on another machine isn't really an option as I would like the gateway option so I can also evaluate connecting to Azure and managing IaaS VMs. Thank you!

    Edward supported this idea  · 

Feedback and Knowledge Base