Running non-Pro version in a corp environment?

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #411,409 by pwhysall 6/27/16 3:02:39 AM 6/27/16 3:02:39 AM Reply	Running non-Pro version in a corp environment? Curious. I thought you couldn't join non-Pro Windows SKUs to a domain?
Post #411,412 by Another Scott 6/27/16 7:51:11 AM 6/27/16 7:51:11 AM Reply	Nope. Home at Home. We have licenses that let us run the corporate AV stuff on our home machines (to prevent cross-contamination and the like). Home doesn't touch the corporate network. Cheers, Scott.
Post #411,416 by pwhysall 6/27/16 1:32:18 PM 6/27/16 1:32:18 PM Reply	Ah, understood. We get the MS Home Use Programme, which let me get Visio 2016 for a tenner. I draw a lot of things in Visio. But yay, antivirus (that you don't need)!
Post #411,417 by Andrew Grygus 6/27/16 1:44:34 PM 6/27/16 1:44:34 PM Reply	"I thought you couldn't join non-Pro Windows SKUs to a domain?" You can't join a domain. I have found though, that a Home version can access shares on the domain as if it was a Workgroup. I used to encounter a lot of sites where some hot shot just out of school set up a small business with the full Microsoft Everything - far more than the owners had any ability to understand or maintain. Then the owners would go out and buy computers with Home on them and want to access files.

Upgraded to Win10 on this Toshiba R835. So far, so good... - (Another Scott) - (4) - June 27, 2016, 12:05:57 AM EDT

Running non-Pro version in a corp environment? - (pwhysall) - (3) - June 27, 2016, 03:02:39 AM EDT

Nope. Home at Home. - (Another Scott) - (1) - June 27, 2016, 07:51:11 AM EDT

Ah, understood. - (pwhysall) - June 27, 2016, 01:32:18 PM EDT

Actually validated for HTML 4.01 Transitional compliance.
69 ms