As some might recall, I ran into Wiztree a month ago. I asked the author to look into adding it to Chocolatey.
And he did.
It's been a good year for Dashrender - down 40 Lbs since January!
Brought my mile time from 8:29 to 6:47.
Only bad thing - good cholesterol is a bit low (but bad cholesterol is in the good range). Doc suggested I drink Red Wine to improve the good Cholesterol.
I was restoring some files from our backups when I ran across this.
These files have been sitting there for a month plus. Unbelievably it appears that non of my other network shares were affected by this.
OMG - I think we some how dodged this bullet.
Just read about this free book on that other site, thought i would share a link to it here.
Let's try this again. You might have seen my other post where I was trying to gather all of the steps for installing Hyper-V 2016 in a domain a bit ago.. Here's my second try.
Install Hyper-V 2016 on a server - very typical Windows install, so I am not including any screen shots.
Typical install will have a 40-80 GB and the rest as the drive.
Upon first boot you will be prompted to create a local admin password. After setting the password you should see something like this.
I'll start by setting a static IP address, option
8 for networking.
In my case only one NIC is plugged in, so that's the only one you can manage via sconfig (the default menuing system you see here).
We want to set the Network Adapter Address, so option 1
We want static, so
Type in the IP address information as requested
Now we set the DNS server, option
2, click OK to continue.
you're prompted for a secondary DNS, enter it if you have one
4 to return to the main menu.
Now I'll join the domain, option
D for domain
Type in the name of the domain, then you're prompted for the user that can add computers to the domain
A new window opens and prompts you for that user's password
You're returned to sconfig and prompted about changing the computer name before reboot, click yes
You're now prompted for a domain account that has rights to change computer names
you can't reuse a computer name that already exists - unlike adding a desktop machine, Hyper-V will simply error indicating that an account of that name already exists
And again with a new black window asking for that user's password.
Prompted to restart to apply change, click yes.
Upon restart, chose option
6 to install updates.
Now we'll enable remote desktop access via the sconfig menu. Option
e for enable, and
1 for the best secure option.
FYI - Remote access via Server Manager is available by default once you join a domain. You'll still likely want remote desktop access though.
This is a Dell server, so I install OMSA - I won't go into details, you can see JB's writeup here
Change firewall to allow remote administration
Enable-PSRemoting Enable-NetFirewallRule -DisplayGroup “Windows Remote Management” Enable-NetFirewallRule -DisplayGroup “Remote Event Log Management” Enable-NetFirewallRule -DisplayGroup “Remote Volume Management” Set-NetFirewallRule -DisplayGroup 'Windows Management Instrumentation (WMI)' -Enabled true Set-NetFirewallRule -DisplayGroup 'Windows Firewall Remote Management' -Enabled true Set-NetFirewallRule -DisplayGroup 'Remote Service Management' -Enabled true Enable-NetFirewallRule -name RVM-RPCSS-In-TCP,RVM-VDSLDR-In-TCP,RVM-VDS-In-TCP
Remote access needs to be enabled on the machine you're remoting from as well as the one you're remoting too,
netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes enables the needed piece from the local side to allow remote access to Disk Manager*
Change the location to store VMs
Launch Hyper-V manager as a domain admin user (or a domain user who has admin rights on the Hyper-V host)
If you haven't already added the Hyper-V host, do so now.
You should see something like this.
Right click on your Hyper-V host and choose Hyper-V Settings
Change the Virtual Hard Disk and Virtual Machine to your desired location
Create a NIC team, even if only one NIC will be it, because it will be easier to add a second NIC later if needed.
You have two options
Get-NetAdapterto see a list of your adapters like this.
To create a team using my output
New-NetLGfoTeam -Name Team1 -TeamMembers "Ethernet 4","Ethernet 3"
Next to Teams, click the drop down and choose New Team
Give the team a name, then choose the desired adapters, you can change any needed settings under additional properties (exposed here)
FYI, the new team may or may not use the settings set above. If doing this remotely, make sure you have either local access to the host, or something like iLo incase the settings are not what you set above.
Configure a vSwitch, right click on the Hyper-V host and choose Virtual Switch Manager
Click Create Virtual Switch
Name your vSwitch, choose External, then choose your newly created NIC Team.
MS calls the first team Microsoft Network Adapter Multiplexor Driver
*If these are the only adapters connected to the network, make sure you leave Allow management operating system to share this network adapter checked.
You're now ready to create your first VM.
@IRJ Very comparable when it comes to price and functionality. We do offer a 3-year warranty that covers the entire UPS and the battery: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/3S.aspx?cx=3
Typical desktop models:
Eaton 3S: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/3S.aspx?cx=3
Eaton 5S: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/5S.aspx?cx=3
The 5S has a nice LCD screen.
We just had a 2.5 hour outage yesterday and I hadn't replaced my desktop UPS yet. I'm ordering this right now (Amazon has it for $200 for the 1500 model.. awesome price!)
So JB and I are working on fixing some sysprep issues. One issue as seen around these forums is that Sysprep gives errors if Candy Crush and other consumerware are installed into the profile of the user running Sysprep.
So I went in search of a way to prevent that garbage from being install ever!
Here's the technet article - https://blogs.technet.microsoft.com/mniehaus/2015/11/23/seeing-extra-apps-turn-them-off/
Basically it says to start with the most recent ISO from MS possible, Install Windows while completely off the net, then create a new key in the registry.
If that key isn't there, create it
Create a D-Word 32 Bit named DisableWindowsConsumerFeatures with a value of 1
After you've rebooted go online. With luck the system won't download the crap ware... I'll be reporting soon with my results.
huh - interesting situation you have there.
Personally - I'd go back to the client and ask - if there is any chance you will need/want more storage in the server, then let's just do it right now. Buy the 2 additional 3 TB drives and let's just start off correctly with a RAID 10.
I'd skip installing Win server 2016 and instead install Hyper-V 2016, then you'll manage it from a Windows PC using Hyper-V manager (might require Windows 10). This also cuts out any concern on licensing - you won't be tempted to install any applications into the VM host OS
Splitting the VM's OS out from it's data really doesn't gain you much. The OS doesn't really impact the use cases you've mentioned here. Personally I'd create a single VMDK 60-80 GB for your VM1 (AD). The data server is the bigger question - one one hand you just make one huge partition for both data and OS, on the other, you can split it, then split the data across multiple VMDKs also - the only reason I mention this is restore time. If it's all one giant disk, you have to restore the whole thing before you can access it, if they are smaller, you can get access to each bit as you restore it.
I probably won't ever need it again, but It took me more than 5 mins surfing google to find it a second time, so I figure a post here will be easier to find.
Removing BE agent 11.x
Some thoughts on removing BE 2012
Well, with a lot of help from @dashrender, I successfully demoted two problem Domain Controllers and fixed my add network printer list not populating. The DC's were two standalone servers and free up two servers for use as VM Hosts.
Congrats. not sure I would make it public that @Dashrender helped though...
+1 for awesome use of meme.
Thanks JB, I love you to man.
@aidan_walsh afaik there is no reason to install it as a role. All it does is create unnecessary licensing dependencies.
The main reason some people do it is for auto activation of guest windows machines. That is no reason to ever do it IMO.
If every physical server is a Datacenter license then it is pretty transparent also.
But I still do not feel that Installing in this way makes sense.
Yep, KMS server to the rescue.
OH but why?
Lets just say cheating wife and leave it there
So, I installed Hyper-V 2012 R2 Server 2+ weeks ago, went through the process of restoring some snaps from my backup server (good learning process).
Overall the experience was fine, but damn, after managing ESXi for 5+ years with a single pane of glass - who in their right mind wants to manage Hyper-V servers using MS's free tools. That was just ridiculously painful!
I did download 5Nine's Hyper-V manager earlier today, but meh - if I have to use someone else's tool to manage the server, why not just cut all ties and go directly to XenServer?
So I am.
OK 30-40 mins in and XenServer is now booting from the SD card for the first time.
and of course I screwed up and choose the SD card for the VM storage - rebuilding again this time picking my RAID 10 for the VM storage. - it's almost done.
The only digital downloads I aware of are the VLSC licenses.
Otherwise the trial download might let you enter a real key and activate. I'm pretty sure it will. You would want to stand up a trial and then be force to scrap it if you decides to keep it, bit I suppose stranger things have happened.