@WLS-ITGuy said in GPO issue:

@flaxking said in GPO issue:

So the library GPO is linked somewhere above this user's OU and is using security filtering to apply to the library security group only?
Have Domain Computers been given read permission?

Not sure if I understand your questions exactly, I'll post some screenshots when I get back in the office.

That question is due to the topic discussed here: https://blogs.technet.microsoft.com/askds/2016/06/22/deploying-group-policy-security-update-ms16-072-kb3163622/

It sounds like you don't actually have things set up that way though so probably not the problem.

@WLS-ITGuy said in GPO issue:

@flaxking said in GPO issue:

So the library GPO is linked somewhere above this user's OU and is using security filtering to apply to the library security group only?
Have Domain Computers been given read permission?

List of GPOs:

GPOs in the OU:

OK so the user is in the WLS-Faculty group. The two GPOs there will apply. It sounds like that is happening as expected.

You say the user is a member of the library group but I don't see you mention where that group lives in the AD structure. Is the library group in the WLS-Library OU?

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

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

@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.

I spent a fair amount of time trying to figure out what was going wrong and never saw anyone else with a similar problem in all my searching.

I don't get the impression that this is common at all. Most people seem to think they just work and are an upgrade on old school roaming profiles.

I don't think I'd let the one anecdote of trouble rule it out as an option unless you are in an extreme hurry.

As much as Scott is likely against this - I would have request permission to open a case with MS - The $250 call would have likely provided you direct access to MS engineers to assist in the issue. I'm guessing you could have saved a lot of money (i.e. your salary time) getting to a solution faster - and if not, then MS would refund your money, but at least you would have had them sitting side by side with you working the issue.

A coworker spent some time with MS support as I recall. Since I wasn't involved in the call(s) I don't know how well that was handled on either end but we didn't get a resolution.

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

@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.

I spent a fair amount of time trying to figure out what was going wrong and never saw anyone else with a similar problem in all my searching.

I don't get the impression that this is common at all. Most people seem to think they just work and are an upgrade on old school roaming profiles.

I don't think I'd let the one anecdote of trouble rule it out as an option unless you are in an extreme hurry.

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

@NDC Our main pain with them was "Disk was surprised removed" messages in the Event Logs and the occasional Session Host that refused to let the UPD go after the user had logged out that brought about a support call.

The problem here was that I couldn't get them to reliably connect at logon.

I've seen that this is typically caused by the UPD not being unlocked properly after the last session but so far as I could tell ours were not locked.

I used the MS tool for checking up on such things and could see the system lock an open disk when logon began, then unlock it 1/2 way through the process, leaving the user at the desktop with a temp profile.

This would happen to test users after a week of successful logins. Some accounts it seemed to get stuck that way more or less permanently, others would switch back and forth between success and temp profiles seemingly at random.

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

FSLogix is now included with Remote Desktop Services CALs.

I totally missed the announcement on that. At one point it was being looked at here but dropped for cost. Will have to look again.

UPDs were a bit dodgy when we experimented with them but I'm reasonably sure that was due to GPO cruft. Hoping to get that cleaned up for another attempt soon.

@Obsolesce said in Microsoft Office - Licensing Questions For 3 Scenarios:

@JaredBusch said in Microsoft Office - Licensing Questions For 3 Scenarios:

@NDC said in Microsoft Office - Licensing Questions For 3 Scenarios:

@wrx7m said in Microsoft Office - Licensing Questions For 3 Scenarios:

@Obsolesce said in Microsoft Office - Licensing Questions For 3 Scenarios:

@wrx7m said in Microsoft Office - Licensing Questions For 3 Scenarios:

Scenario 1

You need to install O365 on that machine using the shared option. Forget the name atm, not at a PC.

What happens is when they log on to the computer, office asks them to log in.

They'll need to have their own login for that computer.

Technically, doing it this way is the only allowed way to do it. You must specifically install the shared version of office.

Edit: found the link
https://docs.microsoft.com/en-us/deployoffice/overview-of-shared-computer-activation-for-office-365-proplus

I have read that, and the shared activation is for proplus. We have business premium. So, we would have to assign users with proplus licensing. However, a chat with MS last night yielded no solution. Sure, you can use proplus to do this, but what about if you have those same users that have office 365 mailboxes/exchange online with business premium? They couldn't answer that.

I read that MS has expanded the selections that can do shared activation somewhere. I want to say that happened in April? Here we go MS blog about the change.

Boom, win.

Which links right to the article I posted 3 days ago...

Sorry saw a bunch of links to info about shared activation but missed that one. Yup already covered I guess.

@Obsolesce said in Microsoft Office - Licensing Questions For 3 Scenarios:

@JaredBusch said in Microsoft Office - Licensing Questions For 3 Scenarios:

@NDC said in Microsoft Office - Licensing Questions For 3 Scenarios:

@wrx7m said in Microsoft Office - Licensing Questions For 3 Scenarios:

@Obsolesce said in Microsoft Office - Licensing Questions For 3 Scenarios:

@wrx7m said in Microsoft Office - Licensing Questions For 3 Scenarios:

Scenario 1

You need to install O365 on that machine using the shared option. Forget the name atm, not at a PC.

What happens is when they log on to the computer, office asks them to log in.

They'll need to have their own login for that computer.

Technically, doing it this way is the only allowed way to do it. You must specifically install the shared version of office.

Edit: found the link
https://docs.microsoft.com/en-us/deployoffice/overview-of-shared-computer-activation-for-office-365-proplus

I have read that, and the shared activation is for proplus. We have business premium. So, we would have to assign users with proplus licensing. However, a chat with MS last night yielded no solution. Sure, you can use proplus to do this, but what about if you have those same users that have office 365 mailboxes/exchange online with business premium? They couldn't answer that.

I read that MS has expanded the selections that can do shared activation somewhere. I want to say that happened in April? Here we go MS blog about the change.

Boom, win.

Which links right to the article I posted 3 days ago...

Ah indeed upon review it would appear I didn't look closely enough before posting. Sorry.

@wrx7m said in Microsoft Office - Licensing Questions For 3 Scenarios:

@Obsolesce said in Microsoft Office - Licensing Questions For 3 Scenarios:

@wrx7m said in Microsoft Office - Licensing Questions For 3 Scenarios:

Scenario 1

You need to install O365 on that machine using the shared option. Forget the name atm, not at a PC.

What happens is when they log on to the computer, office asks them to log in.

They'll need to have their own login for that computer.

Technically, doing it this way is the only allowed way to do it. You must specifically install the shared version of office.

Edit: found the link
https://docs.microsoft.com/en-us/deployoffice/overview-of-shared-computer-activation-for-office-365-proplus

I have read that, and the shared activation is for proplus. We have business premium. So, we would have to assign users with proplus licensing. However, a chat with MS last night yielded no solution. Sure, you can use proplus to do this, but what about if you have those same users that have office 365 mailboxes/exchange online with business premium? They couldn't answer that.

I read that MS has expanded the selections that can do shared activation somewhere. I want to say that happened in April? Here we go MS blog about the change.

@black3dynamite said in What Are You Watching Now:

I can't remember if I'm on episode 3 or 4 but so far David or the character seems off to me. I'm probably trippin, but there's some bromance happening between the two main characters.

The only way in which you might be trippin is that you think maybe it isn't there.

If any of you who are watching haven't read the book previously it is very much worth a go.

Seems pretty likely there would be some form of renewal. I do spot a fee for filing a periodic report which is only $10. I'll have to dig in a bit more and see what else might apply.

I don't actually see a renewal cost for CO. Not sure if we don't have one or I'm just missing it.

https://www.sos.state.co.us/pubs/info_center/fees/business.html#BIZ