Best way to run Chrome on 2016 RDS. Use this as a reference. https://support.google.com/chrome/a/answer/187202?hl=en Use enterprise edition and configure admx with GPO Set Disk Cache Directory Roaming Profiles Directory User Data Directory Setting up Legacy Browsers and Plugin Turning off Hardware accel and other settings for performance. Just read that and configure what policies you need. Took me a day to set up but works smooth.

@wrx7m said in Server 2016 - Force Default Update Server to WSUS Server Via GPO: @dbeato said in Server 2016 - Force Default Update Server to WSUS Server Via GPO: This would have happened on Server 2012 R2 as well, dual scan has been around and causes a lot of problems as you noted. It is strange that I didn't have these issues in 2012 R2. I essentially copied the same GPO for 2012 R2 and made some minor changes to it to convert it for 2016. My 2012 R2 show the correct default service. Weird, I have various Server 2016and now 2019 with WSUS and while dual scan was an issue for me on Server 2012/ 2012 R2 not anymore.

@pmoncho said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?: @Dashrender said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?: Cool, then you should have it easy. FYI - Published apps still create a full profile on the RDS box, Just the desktop isn't presented to the user. If the application allows them to browse around, they could typically see the drive letters, the mapped printers, etc... that's why you still need to lock all that stuff down. Thanks for the info. I will keep that in mind. I was debating about using UPD's like @wrx7m and that was my interest in this post. Also, still planning out where to put Connection Broker, WebAccess and Licensing but that is another post. For local profile management, UPDs are a lot cleaner. If we are not putting them on a file server across the network then a second partition/VHDX is set up for that task to keep them separate. With the inclusion of FSLogix with RDS CALs/SALs now it's a no-brainer, IMNSHO, to set the project up on the FSLogix version. Storage management is another reason why UPDs on a network or separate partition make sense. Keeping a local profile on the C:\ of the session host is messy and can cause issues down the road with users coming and going. As far as the Broker/Gateway/Web put those roles on one VM but separate from the Session Host.

@dbeato said in Reset 120 Day Grace Period for Windows RDS Server with PowerShell: @scottalanmiller I assume you needed to do this while dealing with the RDS CALs on your post about that right? Yeah. They still have not come through, but there is a chance that they might today. We will see.

I would recommend to use the UEFI PXE Boot and that any UEFI boot settings on the devices to be deployed have UEFI settings enabled, including the UEFI Network stack (At least on dell devices). For testing I always run a VM to test my deployments before using on a Desktop and prepare it as much as I can and then deploy it to the devices. It helps to add all the drive packs from the Hardware Manufacturer (Say Dell, HP and so forth). Dell https://www.dell.com/support/article/us/en/04/sln312414/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment?lang=en HP http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x86.html Lenovo https://support.lenovo.com/us/en/solutions/ht074984 Acer https://www.acer.com/sccm/ Microsoft https://docs.microsoft.com/en-us/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices With Pre-Staging machines you need to rely on adding the device mac addresses manually or use Microsoft AD to add them with a Script or Manually to be ready to WDS. This makes it that you can add the devices before hand and only those devices will get the deployment. However you can setup an specific network or VLAN to have the WDS For Multicast, I like this article https://specopssoft.com/blog/wds-multicast-configuration/ However I like the option to disconnect the clients when their speeds go way low and then go unicast instead of multicast. Multicast makes sense that way that way the slow clients do not slow the faster clients. I am still not sure why MDT is not being implemented but that is for another post.

@scottalanmiller said in Let's Encrypt Windows Server: @WLS-ITGuy said in Let's Encrypt Windows Server: @JaredBusch you don't have any issues with agents checking in or pushing out updates with the RP? What would be the concern? Curious more than anything.

Not yet.

@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain: @scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain: @Dashrender said in Need to Join Windows XP Clients to a 2016 Domain: @scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain: @Dashrender said in Need to Join Windows XP Clients to a 2016 Domain: Does the XP machine need to be part of the domain? What about working around that issue? We removed the domain completely. So now you're what - trying to use a 2019 SMB file share or something? What does file share have to do with AD? Completely disconnected concepts. True - I was making my own leap - So - where does this stand now then?? We removed AD. It turned out that it had been installed without evaluation and was serving no real purpose, but was posing a significant risk.

@pmoncho said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host: @JasGot said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host: Winner Winner, Chicken Dinner. It was MDTC and Windows Firewall. (Which is frustrating, because the firewall is turned off for the domain!) Good job at troubleshooting. I'm wondering what led you down this path versus something related to Networking, hard drives or software drivers? Remembered it from several years ago with another SQL based application. Don't know what made me think of it at 1:30am. But I'm ok with it!

@scottalanmiller sorry I wanted to answer @flaxking but ended up replying to yours reply xD

@NerdyDad You can use Loopback Processing also. https://blogs.technet.microsoft.com/askds/2013/02/08/circle-back-to-loopback/

/proc doesn't differ too much with LXC. [[email protected] ~]# ls /proc 1 24924 24951 25368 275 322 bus diskstats interrupts key-users locks net slabinfo thread-self zoneinfo 12471 24925 24952 25369 295 323 cgroups dma iomem kmsg mdstat pagetypeinfo softirqs timer_list 12581 24926 24953 25370 316 54 cmdline driver ioports kpagecgroup meminfo partitions stat tty 24897 24937 24955 25381 318 56 consoles execdomains irq kpagecount misc sched_debug swaps uptime 24908 24938 25157 25382 319 69 cpuinfo fb kallsyms kpageflags modules schedstat sys version 24909 24939 25258 25383 32 acpi crypto filesystems kcore latency_stats mounts scsi sysrq-trigger vmallocinfo 24910 24950 25286 25386 320 buddyinfo devices fs keys loadavg mtrr self sysvipc vmstat [[email protected] proc]$ ls /proc 1 112 2 24453 24612 31 38 427 532 644 674 759 acpi diskstats ioports kpageflags mtrr softirqs uptime 10 12 20 24455 24613 32 39 428 557 645 676 8 buddyinfo dma irq latency_stats net stat version 100 13 21 24460 24621 326 393 429 598 646 677 9 bus driver kallsyms loadavg pagetypeinfo swaps vmallocinfo 101 13532 21810 24461 2599 33 4 43 599 647 681 9133 cgroups execdomains kcore locks partitions sys vmstat 102 14 22 24510 27 332 403 430 6 648 682 9214 cmdline fb keys mdstat sched_debug sysrq-trigger zoneinfo 103 15 23 24512 28 34 421 431 612 654 683 968 consoles filesystems key-users meminfo schedstat sysvipc 105 16 23974 24520 29 35 424 432 613 659 684 969 cpuinfo fs kmsg misc scsi thread-self 106 17 24 24562 3 36 425 44 615 662 694 98 crypto interrupts kpagecgroup modules self timer_list 11 18 24449 24568 30 37 426 517 643 664 752 99 devices iomem kpagecount mounts slabinfo tty Container on top. KVM on bottom.

Thanks all

@CCWTech As an alternative, you can try this tool: https://www.uwe-sieber.de/usbdlm_e.html

I finally got this to work if anyone is interested. The sql file is fine, but I had to change my batch file. The correct one looks like this: "C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\sqlcmd" -I -S \.\pipe\MICROSOFT##WID\tsql\query -i C:\Scripts\WSUSDBMaintenance.sql It must be run from an Administrator command prompt. This took me several days to figure out so I hope it can benefit someone else. Everything I found about reindexing the WSUS database was on Server 2008 or 2012. This works on Server 2016.

@nerdydad - Yes, you do get a skimped down version of Azure AD with the O365 license. The prerequisites mention using Azure AD, but don't say which one, except where they say that the Premium version is optional for auto enrollment with intune. Although, they have several plans/tiers, including 2 premium tiers.

@phlipelder said in Hyper-V Server 2016 guest licensing question: The guests on an OEM licensed host can be moved to another host whether it's licensed OEM, VL, or Retail so long as the destination host is licensed to receive those guests. That makes no sense. That's not moving it, that's buying it twice. Very different things. That's like "can I move my house from here to there"? People mean take the same house and shift its location. Not buy a second house in the new location and give up the old one.

@emad-r said in Trying to correctly understand core licensing in a vmware environment: @dave247 maybe this was answered here, but I was wondering if someone can correct me on this If i put WIndows server VM with 2 cores on Hypervisor any brand which has 8 cores. Do i need to license windows server VM for 2 cores or 8 cores ? There are no cores at the VM level, those are vCPUs. Windows is licensed by cores, not by vCPUs. Cores are always physical, and the minimum is 16. No matter how you configure the VMs and vCPUs, you have to license 16 cores at a minimum. A single vCPU could use sixteen cores or more to power it, the licensing is by the available power, not the configuration.

@bnrstnr said in Annoying Apple Issue - SMB - Finder issue: @dustinb3403 This doesn't even sound like a bug, more like intentional crippling. Is there some proprietary Apple file sharing protocol they want people using? Well, there is speculation of that. But it is not documented and Apple kept it even after their reasons for doing so (promoting their own SMB server that addressed it with a patch) were gone. It's known as a "bug" and Apple has admitted to it as a bug that they don't care to fix. So.... read in as you will.

@nashbrydges said in Microsoft HTML5 Web RDS Client: Wonder if this will be better than my Apache Guacamole install for RDP. Likely, only because it needs one fewer components in the chain. But less flexible.

@dustinb3403 said in Phoronix Publishes Windows vs. Linux Network Benchmarks: That is surprisingly disappointing. Server 2016 is supposedly the best thing ever. . . Of course it is, if you get paid to support it!

@nerdydad said in MS Windows Server 2016 Datacenter not activating: @aaronstuder said in MS Windows Server 2016 Datacenter not activating: @nerdydad any firewalls in the way? No firewalls this go around. There have been some network changes, but nothing in the way of firewalls. @tim_g said in MS Windows Server 2016 Datacenter not activating: @nerdydad said in MS Windows Server 2016 Datacenter not activating: Have a MS Windows Server 2016 Datacenter that won't activate. I have tried GUI in system properties and settings and have tried DISM. Ran for updates and all patched up. Tried activation again, and not working. Anybody have any ideas? What's the error you get? Typically it was that it can't upgrade the server to that licensing because it was already there. @black3dynamite said in MS Windows Server 2016 Datacenter not activating: Have you tried activating using Windows Software Licensing Management Tool? slmgr.vbs I didn't know this existed, but will hold on to it for the future. Thanks. The SLMGR is awesome https://blogs.technet.microsoft.com/askcore/2016/10/19/windows-server-2016-volume-activation-tips/

@dashrender said in Windows Server 2016 NIC Teaming - No internet: @thwr said in Windows Server 2016 NIC Teaming - No internet: @tim_g said in Windows Server 2016 NIC Teaming - No internet: @thwr said in Windows Server 2016 NIC Teaming - No internet: @tim_g said in Windows Server 2016 NIC Teaming - No internet: Are you setting the NICTeam IP or one of the adapters making the team. Leave the individual adapters alone, and just set the Team Asked that before, he's configuring the team, not the NICs Before it's a team you can mess with the NIC settings, and it effects the Team afterwards (in my experience). Should not happen because Windows will unbind all IP protocols (v4 and v6) from each member NIC. At least in theory. Don't ya just love theory??? I'm more on the practical side.

@r3dpand4 said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: @tim_g said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: @scottalanmiller said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: @darek-hamann said in Microsoft Removes Storage Spaces Direct from Windows Server 2016: The implementation of an Azure Stack would be something to get our heads around for the time being. Hopefully it is better than the actual Azure system! It is Azure, same thing, but you have a physical node on-prem. You pay for the hardware, and you get Azure a little cheaper, but it's fully managed by them. It's really only for remote places with bad bandwidth imho. Think like, needing cloud from an 18-wheeler in a remote location. This sounds like a crappy version of the AWS Snowball Completely different. This is like making your portion of the AWS cloud in-house, including the entire AWS stack. Again, not too useful unless you are trying to bring the cloud to a remote location to avoid excessive latency or to somewhere the internet doesn't exist... like linking it to a satellite connection during a disaster or something. There are other real uses, but that would be for bigger enterprises... for most SMBs, Azure Stack would never be a consideration.