Windows 10 in the Enterprise

korgtronix said:
I think you only get a choice of core or minimal gui now. The minimal gui is pretty good if you dont know all of the powershell commands as you can still access the old gui stuff.
Click to expand...

Odd decision by MS. One of the main benefits to windows server was the gui and now they want to go all command line, in that case i might as well move to linux as it has a far better console.

I didn't see any powershell though, it just got stuck on a cmd window.

Great so running powershell commands all day... i hate microsoft.


Lol MS gone full retard, they went from fullscreen start menu to powershell only. Imagine installing and configuring exchange or sccm with powershell commands only. What a nightmare, time to find a new career path i think.
 
Last edited:
Ridiculous waste of everyone time.


Typical microsoft, microsoft idea of security remove explorer. lol

Ok say i went with it, how would i go about installing mdt 2013 on to this gui-less version of windows server? How to download the setup files?


The comments on that article are great. haha
 
Last edited:
anything I don't mind said:
Lol MS gone full retard, they went from fullscreen start menu to powershell only. Imagine installing and configuring exchange or sccm with powershell commands only. What a nightmare, time to find a new career path i think.
Click to expand...


To be fair its all gone remote admin or web based. GUI front ends will soon be a thing of the past when it comes to servers, even more so now there pushing Docker. its all down to security and having the smallest foot print!

Though saying that powershel is great but i find myself using it as little as possible, i can appreciate the sheer power of it but its frustrating in its terminology!
 
Powershell sucks.

There is many windows based software that does not support powershell and requires gui.

Even microsoft functions require explorer, file ACL management.

Even basic things like downloading and install software will require a gui. Even MDT requires a gui and sccm.

You can't even manage MS own products without a gui and yet its now the default option?

I don't need to manage my servers with powershell i only have 20 of them. I rarely add and remove features and when i do i do it with the gui not remotely via powershell.

Its not like removing explorer is going to make windows any more secure, we will still have 10 security updates per month and someone could just as easily get in to the server and run all powershell commands remotely. In fact most attack vectors come in the form of remote command line attacks via dos and powershell. Rarely does the gui get taken over as a first point at the server level.

MS realy ignoring the small and medium business market with this decision. They are prioritising their azure solutions over their existing markets, trying to push everyone to pay them even more money to run servers on their over priced hosting than have their own servers. This is why they are doing this.

This idea that everything is going remote admin or web based is meant to have been happening for yeasr now but many enterprise software still rely on windows gui. Even microsoft does with file servers and similar.

Another bad move by MS.
 
I think your looking at the reasoning behind the lack of GUI, there are several reasons for it such as.

Reduced footprint in storage and memory usage.

There is the ability to enable and disable the GUI as an when you like so if there is a piece of software that needs to be installed it should be a problem.

I suspect that most server software should provide some remote administration capabilities so install can be done via deployment and then management/setup can happen remotely.

Less services are ran on a core install so less possible services to hit in an attack.

As for Powershell sucking your need to actually use it to its full potential to full appreciate it. It partly is about executing commands and one liners.
But when you move into managing/reporting on more than one object/system you can leverage the scripting capabilities to speed up what would normally take say hours to days into minutes.


anything I don't mind said:
Powershell sucks.

There is many windows based software that does not support powershell and requires gui.

Even microsoft functions require explorer, file ACL management.

Even basic things like downloading and install software will require a gui. Even MDT requires a gui and sccm.

You can't even manage MS own products without a gui and yet its now the default option?

I don't need to manage my servers with powershell i only have 20 of them. I rarely add and remove features and when i do i do it with the gui not remotely via powershell.

Its not like removing explorer is going to make windows any more secure, we will still have 10 security updates per month and someone could just as easily get in to the server and run all powershell commands remotely. In fact most attack vectors come in the form of remote command line attacks via dos and powershell. Rarely does the gui get taken over as a first point at the server level.

MS realy ignoring the small and medium business market with this decision. They are prioritising their azure solutions over their existing markets, trying to push everyone to pay them even more money to run servers on their over priced hosting than have their own servers. This is why they are doing this.

This idea that everything is going remote admin or web based is meant to have been happening for yeasr now but many enterprise software still rely on windows gui. Even microsoft does with file servers and similar.

Another bad move by MS.
Click to expand...
 
anyone else having bother getting hyper-v manager to connect (to 2008R2 server in this case).

complaining about winrm?
 
Powershell really does not suck, it's a extremely powerful tool if used correctly.
With "core" servers (non gui), all you need is to give it an ip, change it's name and add it to a domain. Once that's done, type a one line command to enable remote management and use admin tools to do everything you need.
Yes it's a slight pain but if that's the way they are moving then you need to become accustomed to it.
 
MDT is not supported on core servers, so have to install the gui anyway.

Core servers just sounds like a head ache for no reason. It sounds like it would just make more work for myself because I continuously have to use the command line to do things that i could do with my eyes closed previously.

A great example would be permissions. Do you do all your permissions using command line tools then, on core servers. Maybe file servers are not supported on core serves. The not supported list seems to be growing more and more.
 
Are there any good tutorials for Powershell?
Very much a gui person, so might need to start brushing up a few new skills!
Exchange console gives me headaches too.
 
We are a long way from even considering Windows 10 at work, we're only 18 months or so out of our Windows 7 refresh. Though we have 8.1 on touchscreen laptops, we won't be deploying it widely for a while yet.

Powershell is a fantastic tool for scripting, and we use it extensively for that. As a replacement for a GUI it's got a way to go.


############
I was quite keen on Windows Core Server when it first came out.
As a sysadmin with plenty of history using Netware I was expecting something similar - a nice, low footprint OS with a Textual User Interface.
The reality was it was just a command line.

This was with 2008R2, so things may have changed since then, but just to illustrate how really dumb it was here's the command required to install IIS:
(To rub salt into the wounds, iis.net say 'type the following command into a script')
Really Microsoft said:
CMD /C START /w PKGMGR.EXE /l:log.etw /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS-ApplicationDevelopment;IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-ServerSideIncludes;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;IIS-ODBCLogging;IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication;IIS-ClientCertificateMappingAuthentication;IIS-IISCertificateMappingAuthentication;IIS-URLAuthorization;IIS-RequestFiltering;IIS-IPSecurity;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic;IIS-WebServerManagementTools;IIS-ManagementScriptingTools;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-LegacyScripts;WAS-WindowsActivationService;WAS-ProcessModel;IIS-FTPServer;IIS-FTPSvc;IIS-FTPExtensibility;IIS-WebDAV;IIS-ASPNET;IIS-NetFxExtensibility;WAS-NetFxEnvironment;WAS-ConfigurationAPI;IIS-ManagementService;MicrosoftWindowsPowerShell;NetFx2-ServerCore;NetFx2-ServerCore-WOW64
Click to expand...

My brave experiment didn't last beyond that
 
haha brilliant and with no copy and paste with vmware that would realy have to be typed out if you were in situation say where RSAT was not available for your current os. I assume its possible to do a remote connection with a powershell from a non domain laptop for example.

I thought of a scenario where core server would just fail, is if you had it on your dcs and there was a problem that prevented them from starting up (say in a server shutdown window) and you had no access to remote management to diagnose the problem due to the DC being down. Only having the physical terminal access via powershell to diagnose the problem would be impossible, as it comes with no event logs nothing. Then what?
 
anything I don't mind said:
haha brilliant and with no copy and paste with vmware that would realy have to be typed out if you were in situation say where RSAT was not available for your current os. I assume its possible to do a remote connection with a powershell from a non domain laptop for example.

I thought of a scenario where core server would just fail, is if you had it on your dcs and there was a problem that prevented them from starting up (say in a server shutdown window) and you had no access to remote management to diagnose the problem due to the DC being down. Only having the physical terminal access via powershell to diagnose the problem would be impossible, as it comes with no event logs nothing. Then what?
Click to expand...

Running a few core servers in my homelab and they do have eventlogs just have to query them. The minimal gui allows the running of server manager and gui programs from the command line i.e. services.msc will open the gui services.

Powershell is much better now that it was in 2008r2. Play with it there is tonnes you can do with it once you learn.
 
Depends on how your setup and what your trying to accomplish, if its a one of share or file then the gui would be the better option. Again this can be done from another server.

But for say mass changes to permissions or a repeat on permissions but using a variable then powershell would be better than going through each folder permission at at time.

anything I don't mind said:
MDT is not supported on core servers, so have to install the gui anyway.

Core servers just sounds like a head ache for no reason. It sounds like it would just make more work for myself because I continuously have to use the command line to do things that i could do with my eyes closed previously.

A great example would be permissions. Do you do all your permissions using command line tools then, on core servers. Maybe file servers are not supported on core serves. The not supported list seems to be growing more and more.
Click to expand...
 
nick5ter said:
Depends on how your setup and what your trying to accomplish, if its a one of share or file then the gui would be the better option. Again this can be done from another server.

But for say mass changes to permissions or a repeat on permissions but using a variable then powershell would be better than going through each folder permission at at time.
Click to expand...

Ok sure you can do permissions through UNC if its shared. Which it will be in most cases.

I will still miss the gui on the host because it is convenient. It also means that i will have to always have administrator write access to every share and folder. I guess i did over state the impact.

The reason it annoys me is because using a gui is easy and less work and having to learn icalcs if i could avoid it for the rest of my life, that would be great. It just seems the way MS is going i will eventually end up using that because there is no alternative. Then i might as well go in to linux support in my opinion. If i have to write powershell scripts and spend all day working with (a type of) shell then I might as well go with linux/unix support. The main factor that made windows support so popular is that it had gui that was not always basic and user friendly but made the work easier.
 
We just use cores for dc's only. Everything other type of server minus the linux boxes get gui's.

Personally I love powershell, soo much quicker and easier to have reporting running through it rather than old vbs/bat methods.

If you are doing fileservers, surely you want the whole desktop experience put down for the clean up tools and so on, so you can get those special permissions just right?

Just moved my work laptop over to 10 Ent, I've been sitting on 8 for too long due to a legacy Citrix online plugin that I prefer over the newer versions which 10 seems to mostly work fine with (fullscreen mode has disappeared though :<, making do with full window on second screen).

Little hindrances like getting my head around the new start menu and what pinning actually does as opposed to where I thought it would put my shortcuts.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom