I though you were aware of that, but i thought you would prefer the automated version. Maybe I'm biased because in start menu I find way more useful the frequently access list than sticking links manually... P.S. perhaps, funnily enough, I have a close friend which is definitely a delphi wizard, and has spent 3/4 decades coding in Pascal/Delphi &C. Now he is forced to work with .net because a new client, and he isn't the happiest person in the world. I guess it's your turn
You guys are lucky: we only have ~30 terrestrial channels here, so no need for favorite lineups at all with so few channels (on a more serious note, .NET has changed quite a lot since it was open-sourced by MSFT. It's really a great platform to work with in 2023)
I'm used to keep the list small from NPVR and or DVBlink (which is way easier than from WMC itself), then, with the latest H265 development, I have configured everything before your nice tool, so adding every channel was a lot of work so I further reduced the list to the channels I *really* watch, so over my 350 channels I selected about 40 of them. Aside the normal change of habits that are usually unpleasant especially for non teenagers, he don't blame the environment/language per se, he blames more inconsistencies in documentation, and things that are supposed to work but actually aren't, because small quirks that long time .net coders learned over the years, and are used to, while he has to learn them quickly and all at once, to go ahead in his project Just my (second hand) 2 cents.
Yeah, every platform has it own learning curve but MSFT has been investing a lot of time in the docs lately and many of the pitfalls you describe have been eliminated or more clearly documented. That said, we mentioned .NET, but if C#, F# or VB.NET are not your cup of tea and you're a PowerShell fan, using the MCE .NET APIs is not terribly complicated (which is not surprising since PS is based on .NET Framework or .NET Core for the most recent versions): Code: using module C:\Windows\ehome\mcepg.dll using module C:\Windows\ehome\mcstore.dll using namespace System.Security.Cryptography using namespace System.Text using namespace Microsoft.MediaCenter.Store using namespace Microsoft.MediaCenter.Guide $algorithm = [SHA256]::Create() try { try { $store = [ObjectStore]::Open("Anonymous!User", [Convert]::ToBase64String( $algorithm.ComputeHash([Encoding]::Unicode.GetBytes( [ObjectStore]::GetClientId($true))))) try { $lineups = [Lineups]::New($store) foreach ($lineup in $lineups) { Write-Output $lineup.Name } } finally { $lineups.Dispose() } } finally { $store.Dispose() } } finally { $algorithm.Dispose() }
Which features? You can always install enterprise and SKUwitch to WMC, or (never tried that combination personally) you should be able to SKUwitch to 7 Enterprise that is WMC enabled (I feel dumb but I discovered that only recently)
Does prowmc product policies will break some Enterprise features (such as sideloading Metro apps, Windows To Go, AppLocker, DirectAccess, BranchCache, Subsystem for Unix-based Applications, and etc that 8.0 Pro with Media Center lack)?
I'm afraid I never used a single one of this list, except win2go just for couriosity a decade ago. As usual the best way to test your personal needs is to test personally
Also does Windows Storage Server 2012 R2 Essentials exist? As I see only Storage Server 2012 R2 Standard and Workgroup, so, which one is the best for WMC?
Yes I used it for years. It's practically a server standard with a different branding WMC run more or less the same in any windows. So choose the windows you like/need and then install WMC on top of it.
I think features like Bitlocker TO GO, Applock, Brandcache, Domain Creation, etc are exclusive to enterprise SKU. Plus, im not sure if novice user can have an understanding of using tools like skuswitch. Wish there'a a patched WMC for Windows 8 RTM Enterprise and possibly for Vista Enterprise as well apart from the 8.1's one which can be used to deploy it in 8.1 Enterprise and in Newer Windows.
I see. But im sure someone out there, and possibly many companies rely on these features. so i believe its essential to have these features intact since it can benefit someone or many ppl.
Can you send me storage server 2012 r2 essentials in DMs? Because I can only find storage server 2012 r2 standard and workgroup (or one of them is the one which is essentials?)
Download the standard or the essentials. To do what you want to do either are both fine. The download links @ tecus for WSSe images seem dead (looks like they sell just Linux NAS now) wsse_atom_v2.2_en_20160104.iso wsse_w5810_en_20151231.iso Feel free to find them by yourself, if you have time to waste.
Exclusive means nothing. Some features in some SKU are not there because a missing package, some don't work because a Kernel policy. Given both adding packages and SKUwitching are non destructive process, and very quick to test, just test them. No one (including MS people) has experience with all the feature that Windows can offer across all the SKUs, so ynless you're very lucky to find a person with your specific need, test yourself is what you need to do. But (to be sincere) your request sounded more like a quick list find using Ggogle, rather than a real personal need. So we wait for genetically modified users who born already experienced, or we can use the good old method of, testing, learning, experimenting, growing?
It's not like you ask a question four times you get four different answers... For the last time. For server 2012 r2 you need the wsemp package and the wsemp package installs only on Essential flavors and in the Standard/Datacenter if the Essentials role is enabled. Storage Workgroup has not the essential role installed or installable. Then you can patch SKUwitch/ add/remove roles, turn windows inside out, but unlike non existing SKU like my server 2020, that brings a mix of features that you can't get fom MS no matter hou much you pay, in 2012R2 case patching a SKU to get something that is virtually identical to a SKU readily available would be just a waste of time. Perhaps deploying and booting any windows in a half decent machine of this decade (as native vhd or as a Hyper-V machine) takes 5/10 minutes, so why not spend your time experimenting yourself? Maybe you wouldn't reach your goal, but you'll learn 10 times more things than asking and waiting.