A client has Windows Server 2016 Essentials. He installed 128 GB RAM in his server. But Windows reports that it uses only 64 GB even if it sees the whole 128 GB installed
Why? What can be done to use the whole RAM available?
I am trying to determine which version of SMB/CIFS is in use by clients attached to shared folders on my Windows Server 2016. If I run the powershell command Get-SmbConnection on the Windows Server, it will show the SMB version in use on shared folders that the server has connected to, not the SMB versions of clients connected to it.
I have 8 HP ProLiant DL380 servers that are mounted in a data center. I have to deploy Windows Server 2016 Datacenter operating system on all of them using a particular customer's (modified) ISO.
Unfortunately, the only way I can access this installation ISO is inside the DC security zone, which means I will have to create a bootable USB drive on-premise to install the farm. Another problem is that according to customer's SLA using any additional software for creating bootable drives is prohibited. Is there any way of creating a Windows Server 2016 bootable USB using only native Windows 2016 Server tools?
Thanks in advance!
We just got our dedicated server from Rackspace. It was loaded with W2008 on it. I decided to put the most recent OS on it so I wouldn't have to upgrade it later. Apparently during the installation, I selected the no gui option.
I tried to install the gui from powershell that I've seen reference on other website.
For example:
Install-WindowsFeature Server-GUI-Shell -Restart
When I run this, I get the following error:
PS C:\> Install-WindowsFeature Server-GUI-Shell -Restart
Install-WindowsFeature : ArgumentNotValid: The role, role service, or feature name is not valid: 'Server-GUI-Shell'.
The name was not found.
At line:1 char:1
+ Install-WindowsFeature Server-GUI-Shell -Restart
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (Server-GUI-Shell:String) [Install-WindowsFeature], Exception
+ FullyQualifiedErrorId : NameDoesNotExist,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand
Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
False No InvalidArgs {}
I cannot seem to figure out how to get a gui installed on this server.
All references I've seen to installing the gui say to use the Server-GUI-Shell.
Anyone have any suggestions?
We have a 2012 server that has about 20 scheduled tasks that are used for monitoring. We have built a 2016 server to replace it and as I move tasks to the new server I have run into an issue. Most of our tasks run every few minutes.
In Server 2012 we would schedule the task to start at 1200AM of the current day (so a time in the past) and reoccur every X minutes. The task would start at its next scheduled time. Perfect.
In Server 2016 schedules that start in the past don't run. So we had to schedule it to start in the future. This is fine until you reboot. Now the start time is in the past and it won't run. It doesn't even register a failed run. The Next Run Time column shows that it should run but doesn't.
Besides creating two triggers, one that starts in the future and another that starts on reboot (which we don't want to do since some tasks should only run at specified times), is there a better way? This seems to be a bug. The 2012 version worked great.
UPDATE
There is a workaround for this. Create a one time schedule that runs indefinitely. This works after restarts just like you would expect. I know this isn't great for schedules that are "weird" but works fine for things that we want to run every 3 minutes or whatever.