@wrx7m said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@black3dynamite said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@wrx7m said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@dafyre said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@dafyre said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@pmoncho said in RDS - Suggestions for Migrating User Profiles from Server 2008 R2 to Server 2016 UPD:

@wrx7m

Just curious, when you chose UPD, did you choose to store all settings or just certain folders?

Some applications don't play nicely with roaming profiles.

UPDs mount at the usual C:\Users\user.name and the applications can't tell a difference.

Right. But, only when the user is logged in. After they logout, that path doesn't exist. I am trying to figure out how to work around that for adding the custom (for each user) erp shortcut on their desktop in their session.

Add the shortcut to C:\Users\Public\Desktop.
That way it will always show up on each user Desktop.

This would be nice and easy, but each user has a custom shortcut- It has a workstation ID in the target path.

https://www.pdq.com/blog/pdq-deploy-and-powershell/
Create a script that creates the shortcut each user Desktop and append the workstation id in the target path.

@gjacobse said in Designing for tech startup: Network, AD, Backup etc:

@DustinB3403 said in Designing for tech startup: Network, AD, Backup etc:

I suppose you could use Storage Spaces Direct (all windows across the entire thing) but I wouldn't consider SSD at all mature nor production ready, especially at this scale.

Thanks, had not heard of this.

DataOn solutions fully support this and vice versa. They are experienced with this kind of scale and much larger.

@dbeato I forgot you are an MSP.

@sickless316 said in DELL PowerEdge T410 - Memory Configuration Issues:

@pete-s how does any of this make my sense at all??? Did anyone even read any of this thread before posting???

You say he CANT use 16gb sticks which he has CLEARLY done already and have worked but instead of giving good answers you guys pressure people to move on because the people commenting on here either can’t read or don’t know enough already...

This is aggravating because every post about the T410 gets cut off with nonsense like this crp...

He used 16gb sticks so remove your comment, or don’t make one and move on if you didn’t have the answer to the question you just made the question more confusing

If you read more carefully next time, you might not become aggravated. What is supported and what works are two different things.

Reason to move on from old hardware is because for companies IT is a business, not a hobby. Spending time on something costs money, so the potential benefit has to outweigh the cost.

@dbeato said in Vultr, Windows & Data center licensing:

@scottalanmiller said in Vultr, Windows & Data center licensing:

@fuznutz04 said in Vultr, Windows & Data center licensing:

@scottalanmiller Right. So being legit in this scenario, would be so cost prohibitive, it's not possible realistically.

Exactly. It's not technically impossible, as long as Vultr would tell you the number of physical servers within the datacenter you are in and/or the number that are in a pool that your workload could be moved to, which might be any within the datacenter, or might be a subset.

Same applies to AWS and Azure I assume correct @scottalanmiller ?

Correct, any cloud.

We have a set of Group Policy Objects that are set up at the domain level with WMI filters in place for two of the three.
The first has all of the key settings for updates that are shared across the board.
The second using a WMI filter to point only to desktop operating systems with the necessary settings in place for all desktop OS versions that we manage.
The third is for server operating systems only. It delimits to download but not update automatically along with a few other settings.

We've been using this setup since I can remember and not once have we hit servers auto-installing and rebooting. It's too risky for that to happen.

In my case I wanted to kill sleep altogether.

c:\windows\system32\powercfg.exe -change -monitor-timeout-ac 0 c:\windows\system32\powercfg.exe -change -monitor-timeout-dc 0 c:\windows\system32\powercfg.exe -change -disk-timeout-ac 0 c:\windows\system32\powercfg.exe -change -disk-timeout-dc 0 c:\windows\system32\powercfg.exe -change -standby-timeout-ac 0 c:\windows\system32\powercfg.exe -change -standby-timeout-dc 0 c:\windows\system32\powercfg.exe -change -hibernate-timeout-ac 0 c:\windows\system32\powercfg.exe -change -hibernate-timeout-dc 0

@wrx7m said in SMBv2/v3 Issues on Windows Server 2016:

@phlipelder I thought that those files were necessary. I guess I will try to block them as long as it doesn't cause issues on the Mac side.

I don't know if they are critical or not. From what I see online files like .DS_Store is just to show metadata to the mac client. This is likely the tag color etc for the Mac Finder, which for me (personally) doesn't matter. But I'm sure it would affect business pretty heavily.

Thanks.

@networknerd said in Server 2016 Redirected Printer Change:

That's a new one I have not seen. We used Epicor ERP 10, and in that product I did see issues with RemoteApp where from time to time the user would not have a default printer selected in Epicor (sounds weird, I know), which would then crash any report they tried to print with an error that value of -1 was not allowed. Getting the user to change the printer to something in their list was the workaround.

Thanks for capturing this. I bet it will help someone else and looks to be already doing so.

YEah, that is what happens for this case, the RemoteApp shows the printer as a question mark. Once you go to File, Printer Setup and DoubleClick the printer then it is all good for the printer but all reporting shows in Portrait mode instead of Landscape mode.

@dbeato said in RDS 2016 Remote App issue:

@dafyre said in RDS 2016 Remote App issue:

@dbeato said in RDS 2016 Remote App issue:

@dafyre said in RDS 2016 Remote App issue:

@dbeato said in RDS 2016 Remote App issue:

I am also leaning to do this:
https://social.technet.microsoft.com/Forums/windows/en-US/96cf9ef3-6ec2-4c7a-9e9f-21aeb6ef794d/remote-desktop-collection-is-missing-properties-i-would-like-to-add?forum=winserverTS

That's essentially why the powershell script does... So you ran the script and you're still not getting correct RDP files from the RD Web site?

yeah, it didn't really work since it is not updating anything on the connection broker. I am going to redo it all...

Curious.

You mean after I finish redoing it?

Just strange that it isn't working. I have Gateway, Web, and Connection Broker on same system here, so that could be part of it.

@thwr said in Flushing GPOs:

@dbeato said in Flushing GPOs:

You need to setup the settings to Delete or changed to not configured, wait until it applies and then delete the GPOs after confirming they are not applied any longer.

Get-Content c:\temp\gpos.txt | foreach { Get-GPO -Name "$_" | Remove-GPO }

http://jeffwouters.nl/index.php/2013/08/remove-group-policy-objects-through-powershell/

I bet you could do something like this to set all GPOs to "on delete remove from client" too

This assumes a txt file with all GPO names. You could also just use Get-GPO

@dbeato said in How to change you Server 2016 Evaluation into a Standard License:

@jaredbusch said in How to change you Server 2016 Evaluation into a Standard License:

I have had to do this a couple times and always need to look up the command.

So I thought I would drop it here so I can search here first in the future.

DISM /online /Set-Edition:ServerStandard /AcceptEula /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

0_1510698622929_63007167-819c-4838-a470-1ec4889d4844-image.png

Technet Article for doing this on Server 2012: https://technet.microsoft.com/en-us/library/jj574204.aspx

Great job on the powershell, others usually do the command prompt.

Right click on Start open Powershell. I use that only because it is default. The command works in both. I have no preference for something like this command.