@PhlipElder said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?:

User Profile Disks whether native or FSLogix, which is now included with RDS CALs by default

Interesting. I need to check it out. Not sure what it does.

@PhlipElder said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?:

We have not deployed anything RDS related without User Profile Disks in close to a decade now.

Gah! I need to get off the seesaw lol. OK. I will test them out to see how well it handles the 3 apps that people will be accessing.

@NDC I just don't want to do the setup twice. Ain't nobody got time for that.

That was fast. No help from them-
"Hello,

Thank you for your inquiry. Please note that our staff is responsible for infrastructure and system critical functions of the platform itself, not for administration of individual instances. You, or members of your project team are responsible for the administration of the VPS instance deployments on your account.

In the event that you have difficulties making a deployment, or performing some other task within your my.vultr.com account portal, please feel free to raise a ticket and we will address any platform issues where applicable.

While our services are self-managed, we do offer an extensive community library of tutorials in our Vultr Docs section which you can review at:

https://www.vultr.com/docs/

Can't find what you are looking for? You can request new articles from our community by visiting this URL:

https://www.vultr.com/docs/request.php"

Put a ticket in with Vultr. I'll see what they have to say.

@wirestyle22 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

@wrx7m Did you use a custom ISO or their image?

Their Fedora 29 image. Then upgraded to 30 using dnf upgrade.

Just disabled the UPD options on the new server. I think I am going to instruct each person to login to the new server to create a fresh profile and just copy in some stuff.

@NDC OK. Thanks for sharing your issues. I am just going to use regular profiles on a standard disk. I don't have time to deal with those types of issues.

@travisdh1 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

@wrx7m Have you asked Vultr support yet?

Not yet. I wasn't sure how common it was. I'll try them.

@scottalanmiller said in What Are You Doing Right Now:

Just back to the apartment from a day of touring Firenze. Learned to make pasta from scratch today. That was so much fun. Heading to Switzerland and Paris tomorrow.

Oh, nice! Fresh pasta is so much better.

@scottalanmiller said in Non-IT News Thread:

@Dashrender said in Non-IT News Thread:

@hobbit666 said in Non-IT News Thread:

Electric cars: New vehicles to emit noise to aid safety
New electric vehicles will have to feature a noise-emitting device, under an EU rule coming into force on Monday.

It follows concerns that low-emission cars and vans are too quiet, putting pedestrians at risk because they cannot be heard as they approach.
All new types of four-wheel electric vehicle must be fitted with the device, which sounds like a traditional engine.

Yup, because people can't be responsible for themselves at all.

It's for the blind.

My car is great for them, then.

Upon boot, I am getting the EDAC skx: Can't Get tolm/tohm error after upgrading my Vultr instances from Fedora 29 to Fedora 30. Has anyone else experienced this? Is there a fix for it?

EDIT: Changed the thread title to reflect my findings in posts 16-21

@jt1001001 Thanks. If you are running from PDQ deploy, you won't see anything. But, if you are doing it from PS/ISE or similar, that would be a great help.

@Dashrender said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?:

@wrx7m 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?:

As this is meant to be used with VDI only, perhaps the expectation is that you would deploy a whole new VDI as the new version, and an upgrade would never happen - OK Fine.. but the profiles used on the previous version would still exist, so.... how do you use them with the new version of Windows 10?

Well, I didn't see that it was meant for vdi only. I'm not doing vdi, so I I guess that makes the decision between migrating profiles or recreating them manually.

I over stated - UPDs are meant for RDS and VDI, not normal bare metal desktop style use.

Oh, OK. Back on the table at this point.

@Dashrender said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?:

As this is meant to be used with VDI only, perhaps the expectation is that you would deploy a whole new VDI as the new version, and an upgrade would never happen - OK Fine.. but the profiles used on the previous version would still exist, so.... how do you use them with the new version of Windows 10?

Well, I didn't see that it was meant for vdi only. I'm not doing vdi, so I I guess that makes the decision between migrating profiles or recreating them manually.

@dafyre said in Windows RDS User Profiles - Migrate, Recreate or User Profile Disks?:

I can't speak to the Migration process, but I have an RDS & VDI farm with Server 2012 R2 & User Profile Disks... It works great!

Edit: This was built completely around the use of UPDs.

Thanks for the input, @dafyre. I could try that route. I am just not sure how the apps will handle it. I guess I can try setting it up to test and burn it down if it has obvious issues.

The beauty of virtualization.

I was searching for a way to further automate new Windows system deployments. One thing I kept running into was Windows updating.

I have refined and added automation to my process over the past several years. For Windows 10 clients, my current deployment process involves an MDT/WDS server that has a stock Windows 10 wim file. To customize the deployments, I have a collection of GPOs and PDQDeploy packages for software installation and some other GPOs for policies.

I recognized that one of the consistent pain points was related to getting Windows updates going. I had previously just had a GPO to specify some of the settings for Windows updates, such as, the WSUS server URL/port number and how often to check for updates. I reorganized my WSUS server from quite a few groups, to a much simpler grouping by OS version. With that, I created GPOs that applied to systems based on OS version, using WMI filtering that would automatically add the computer to the respective WSUS OS group.

That helped... but I still had a considerable wait for Windows to start its automatic check-in with WSUS. I also found that even logging directly into the new system and forcing a check for updates would yield a lot of waiting and false reporting that there were no updates available. I found that if you deleted the C:\Windows\SoftwareDistribution folder, it would almost always force the client to recognize that there were new updates to install, although the check seemed to take a considerable amount of time. After all that, I still had to wait for the installations to finish and reboot and recheck.

All that to say, I started down a rabbit hole of PowerShell commandlets and scripts to try and trigger Windows to check for updates, install the approved updates and reboot the system. I came up with 3 scripts that can be run in sequence or used separately, depending on if it is a completely new deployment or you just want to trigger Windows updates to install on established systems.

First, this will speed up the new system deployment process by deleting the contents of the Software Distribution folder-

Stop-Service -Name wuauserv
Get-ChildItem C:\Windows\SoftwareDistribution -Recurse | Remove-Item -Recurse -Force
Start-Service -Name wuauserv

Second, install PSWindowsUpdate (Learn more here: https://www.powershellgallery.com/packages/PSWindowsUpdate/2.1.1.2). Essentially, PSWindowsUpdate allows you to run windows update and control certain parameters of how updates are downloaded and applied and if reboots are performed and even rechecks for updates after the first round of updates have been installed.

Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
Install-Module PSWindowsUpdate -Force

Third, run PSWindowsUpdate. This command tells it to accept (download and install) all approved updates from the WSUS server, automatically reboot, and repeat.

Import-Module PSWindowsUpdate
Get-WindowsUpdate -Install -AcceptAll -RecurseCycle 2 -AutoReboot

There are several parameters to allow you to customize how you want to handle the updates. For instance, you can have it download only, or don't have it automatically reboot.

I added these scripts as packages in my PDQ Deploy server and into the sequences that are run during the initial setup of my newly-deployed systems. I have also started using them on servers cloned from VM templates in vCenter Server. Next, I will be using the 2nd and 3rd to help with automating my routine server patching processes. No more logging into each server, wasting nights and weekends, to check for updates, download and install and reboot; just a couple clicks via PDQ Deploy, the rest is machine time.

EDIT: I should also add, it looks like you need to have PowerShell 5.1.

EDIT-2: If you have problems with Server 2016 (maybe even 2019) going out to Microsoft's public update server on the internet, instead of your WSUS server, you can see this post (https://mangolassi.it/topic/19993/server-2016-force-default-update-server-to-wsus-server) on how to make sure your GPO will force the system to use your WSUS server as its default.

@black3dynamite said in What Are You Watching Now:

Youtube Video

Nick Offerman, FTW!

I am setting up Windows 2016 RDS server to retire an old 2008 R2 RDS server. The server provides access to our ERP system, FileMaker and Fishbowl Inventory for remote users. Each of these applications still only support Server 2016.

I currently have about 30 active user profiles on the old one and they are automatically created and pointed to a D:\ partition. I had forgotten about the newer (than 2008 R2) User Profiles Disk feature and am wondering if I should look at moving to that configuration, or just stick with the current type of config.

Are User Profile Disks the standard now? Are they good, bad or it depends?

If I should just keep doing what I am doing, is there an actual migration process for the profiles
or
should I use something like ForensIT to migrate the profiles
or
just have everyone login to the new server and do a robocopy of certain directories (like the desktop)?

Bookmarking site. Thanks @IRJ!