HDHomerun DVR ... DRM

[KryptoNyte]

With the Win 10 anniversary update, we could no longer create folders on network shares.

[Taddeusz]

Originally Posted by KryptoNyte

With the Win 10 anniversary update, we could no longer create folders on network shares.

That sounds like a network permissions problem. I have no issues at home and I'm running a Windows Server 2012 domain controller.

[BobPhoenix]

Originally Posted by KryptoNyte

With the Win 10 anniversary update, we could no longer create folders on network shares.

I do that all the time on my unRAID servers with my Win10 laptop. Also on my WHSv1 server and Win7 desktops. I believe I have the anniversary update: Edition:Win 10 pro, Version:1607, OS Build:14393.187.

[KryptoNyte]

The IT guy claimed it was a well documented problem with the anniversary update last year. I just know it wasn't possible to perform this simple task on Windows 10.

<shrugs>

[EnterNoEscape]

Originally Posted by KryptoNyte

The IT guy claimed it was a well documented problem with the anniversary update last year. I just know it wasn't possible to perform this simple task on Windows 10.

<shrugs>

I doubt the IT guy was wrong. Not everyone gets hit by everything, but when you do and you look into it, you often find you're far from alone. If you never had the problem, you often don't have any clue how widespread it is.

[stanger89]

Originally Posted by panteragstk

In all honesty, I used sage under a Windows VM, and a physical windows box without issues for years. I used full PC clients though so I didn't have memory issues. This was with v7. Pc clients worked well, but had their own set of issues as others have stated. I'll be using a v9 client PC once I get the theater done in my new house. It will be w7 just for simplicity.

I ran Sage, headless, on windows for probably close to 15 years. Never really had a problem. Getting "away" from Windows wasn't a goal for me in my movie to the unRAID docker, consolidation and simplification was.

When unRAID added virtualization support, I moved my Sage server to a Windows VM to eliminate that old, inefficient, and failing hardware from my system. Then eventually when the Docker stabilized, I switched to that since it's more efficient on the server than having a Windows VM just for Sage.

Originally Posted by KryptoNyte

You really hit the nail on the head there. At our small business, 20 machines or so, Windows 10 has been a living hell. We run 50 to 60 different pieces of engineering software, and you can always tell when Microshaft forces a Win 10 update, because the IT guy has that Windows 10 look of disgust on his face as he runs from machine to machine to patch the problems.

That's really my biggest gripe with Windows 10, that it can just reboot your computer on you without asking. At least on Windows 10 Pro you can disable automatic updates, for a while. But I've had both my laptop and desktop rebooted on me without my permission. Fortunately I never lost any important work, but every time that happens I seriously think about going back to Windows 7.

Other than that though, I'm generally fine with Windows 10.

[GrantEdwards]

Originally Posted by Tiki

That's an interesting comment. I wonder what percentage of Sage installs are headless? I would have guessed that most are not headless.

What do you mean by a "headless install"? The machine I run SageTV on has a keyboard and display, but neither are used by SageTV.

[EnterNoEscape]

Originally Posted by GrantEdwards

What do you mean by a "headless install"? The machine I run SageTV on has a keyboard and display, but neither are used by SageTV.

For the home user crowd I would say headless is any system that's used primary for serving content and is usually not used directly for any purposes other than configuration.

[BobPhoenix]

Originally Posted by KryptoNyte

The IT guy claimed it was a well documented problem with the anniversary update last year. I just know it wasn't possible to perform this simple task on Windows 10.

<shrugs>

I'm sure it is a problem in a corporate environment they have to take a lot more security precautions then what I have.

[KarylFStein]

Um, if you're running in a corporate environment there is no reason why a MS change would make it to your terminal without vetting and approval.

I've been on both sides of the coin--security and development. I started in security and couldn't believe the requests. Then I moved to development and am now pissed at the security folks .

I think that everyone in security should take time in development and vice versa. It has really opened my eyes in any case.

Not that this has anything to do with SageTV...

[phelme]

Originally Posted by nyplayer

Seeking is not all that great on the miniclients.... works flawlessly on the full Clients....

ugh, whenever I hit the "pause" button on my Sony/Android TV remote when in the mini client, Google Play Music starts playing in the background.

[panteragstk]

Originally Posted by phelme

ugh, whenever I hit the "pause" button on my Sony/Android TV remote when in the mini client, Google Play Music starts playing in the background.

Yeah, the "Play" command that the Android TV boxes use is not the same as the miniclient. I've never been able to use the "unassigned keypresses" option so Sean can implement this, but if you are able to that would help us all out.

[scoful]

I have windows 10 clients with TPM and EFI boot - but my server is win8.1 - will that work or do I need to upgrade my server? (Of course it does not have EFI capability or TPM)