Tim Cerling

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  ·  PowerShell » Other PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling shared this idea  · 
  2. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Installation and Patching » WDS & MDT  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling shared this idea  · 
  3. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Core Server » Setup  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    Does this (https://blogs.technet.microsoft.com/nanoserver/2016/10/15/introducing-the-nano-server-image-builder) meet your needs? That allows creation of bootable USB media.
    As to a running instance moving from one server to another, that gets into a licensing issue more than a technology issue. Since a license can be moved from one physical host to another physical host once every 90 days (?), running a system from removable media seems to have limited usefulness.
    Maybe I am missing something in your request? Maybe a more complete explanation of the what and why would help others understand what you are looking for.

  4. 0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  General Feedback » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    Asking for a switch for the mouse. KVM switches have been around for a very long time. This request really has nothing to do with Windows Server. A small investment in a KVM switch will provide what is requested.

  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Tim Cerling commented  · 

    Support for systems comes from the hardware vendor, not from Microsoft. Each hardware vendor runs validation processes against every system they want to support. If you want an Itanium system to be supported, you need to talk with the vendor of the Itanium system and have them run the validation processes. Once that has passed, they can place their system on the list of supported servers at www.windowsservercatalog.com.

  6. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  General Feedback » Licensing, SKU, & Edition  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    Anthony - not sure what you mean here. Windows Server 2016 Standard, even 2012 and 2008, are able to run more than two VMs on a system. The number of VMs that can be run is limited by the hardware on the system. There is nothing in Hyper-V that limits you to 2 VMs on any of these operating systems.
    That said, there is a licensing limitation. Windows Server Standard (2008, 2012, 2016) grant the right for the simultaneous execution of two Windows Server Standard VMs, but it does not enforce any technical limitation to the number of VMs that can be run simultaneously. It does not even enforce the legal limitation of two Windows Server VMs.
    Where are you seeing this restriction?

  7. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  General Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    It only requires two clicks on my TP5 installation. Right-click the Windows icon, move the mouse to 'Shutdown or signout' which automatically opens a menu containing 'Sign out'. Second click on that and I am signed out.

  8. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General Feedback » Licensing, SKU, & Edition  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    On the www.microsoft.com/licensing site, you will see an option on the right-hand side for Licensing Support. Click that and it will expand. Select 'Contact Support for the Volume Licensing Service Center' and you will be able to find the telephone number for your regional support. Give them a call.

  9. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  General Feedback » Shell, GUI, & Explorer  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    I have not found a need for an extensive menu system on Windows Server for quite some time. In fact, I rarely use one on my client systems, either.
    That said, it is a very simple task to maintain your own menu system tailored specifically to your needs. C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools contains the .lnk files that are used to launch applications/utilities from the Server Manager Tools menu. If you want a more extant menu system, you can maintain your own. This provides for both worlds - those who do not need/want an extensive GUI menu system and those that do.

  10. 8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Virtualization » Guest capabilities  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling supported this idea  · 
    Tim Cerling commented  · 

    I would take this a step farther and suggest that the name of NIC take on the name of the switch on which it is defined. For example, if the switch is named 'VMaccess', the first NIC would be called 'VMaccess', the second would be 'VMaccess #2', etc. Taking it even farther would be to implement this as a Consistent Device Naming capability so that the name would pass through to the VM's operating system, meaning that the operating system would have the NICs named just like occurs at the physical level with CDN.

  11. 20 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Virtualization  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling supported this idea  · 
  12. 15 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Core Server » Installation and patching  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling supported this idea  · 
  13. 66 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Core Server  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling supported this idea  · 
    Tim Cerling commented  · 

    I would add SD as a running system device in addition to USB.

  14. 49 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  General Feedback » Configuration  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    Microsoft will support Windows Server/Hyper-V booting from SD or USB for installation media but not running systems. They will support Hyper-V booting from USB if the OEM provides modified USB drivers (https://technet.microsoft.com/en-us/library/jj733589.aspx). Basically the modified driver changes the USB from removable media to fixed media so the installation process will recognize the drive as a drive it can use for installation. Since both SD and USB are seen by the operating system as removable media, installation will not recognize the device. This is a change that Microsoft needs to implement instead of the OEM making a special driver for it.

    Tim Cerling shared this idea  · 
  15. 84 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Installation and Patching » Server Mode  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling supported this idea  · 
  16. 14 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Storage » Work Folders  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    Please provide some information about what you mean here.

  17. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Tim Cerling commented  · 

    Could you provide more information on this request? I looked at a number of my systems and Server Manager was taking only 70-110 MB of memory. What do you consider 'a lot of memory space'? What would you consider reasonable?

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

    We’ll send you updates on this idea

    2 comments  ·  General Feedback » Configuration  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    Could you provide a little more explanation of what you mean? Windows Server 2016 has NTFS and NTFS file security, so I don't know what you mean.

  19. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Core Server  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling shared this idea  · 
  20. 45 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Core Server » Installation and patching  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Cerling commented  · 

    Installing Nanoserver from USB is possible today. Because preparing Nanoserver for installation differs from preparing Datacenter or Standard for installation, the procedure is a little different, but it is possible. First you need to create a USB with a WinPE image that has enabled PowerShell. Then you add the Nanoserver wim. Here is a blog link that is part of a series on a module that was created to make this easier. It is the last in the series, but it has links to all previous posts to cover everything needed. If you don't like using the blogger's module, his process can be readily adapted to using the Nanoserver Quickstart method shown in TechNet. FWIW, I gave it a try and was successful in deploying Nano from a WinPE boot.

    http://blogs.technet.com/b/heyscriptingguy/archive/2015/12/11/using-deployimage-and-windows-powershell-to-build-a-nano-server-part-5.aspx

← Previous 1

Feedback and Knowledge Base