Windows 10 in the Enterprise

Event Logs aren't the only way to diagnose a problem with a system or DC, but having access to the shell from the terminal would be enough. You can query the eventlogs on the system using powershell.

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?
 
Installed MDT 2013 sp1 on windows 10 server and its 100% exactly the same as the older version. I don't know why i am surprised. I guess i had hoped for improvements.

Anyone ever used the "link deployment share option"

This in my opinion is a typical example of how annoying MS is at developing software.

http://www.deploymentwitchcraft.com...0dyn-0x0x100-00f0w010c010r110f110r010t010.jpg

You see the language they use. There is no way to know which side is the target share of the link. It would be very easy to wipe your old deployment share with a blank new one because MS fail to specify exactly which side is the target. Is the local side or the remote side? I know that if i tried to link my new deployment share to my old one, it will end up wiping my active and full deployment share with the new blank deployment share, why because MS loves not being clear. They are so lazy it is ridiculous. Why not just make it clear, say "specify the target deployment share" instead they just say specify unc path of deployment share.
 
Last edited:
Back
Top Bottom