Tutorial: SageTV on WHS with 64K clusters in the drive pool...

[HuMan321]

Originally Posted by gplasky

It will if you have that same account with the same password on the XP machine. As my other post got to My Computer and Manage. Find the Users and Groups and go into the Users folder. Find the user Dad on the right hand side and right-click and choose Properties. Look for the "Members of" tab and you should see Administrators in the list. If not you need to add it to the group. Click the Add button and type in Administrators. CLick the Check Name button and it should give you Machinename\Administrators. Click OK and now the user is part of the Administrators group. Make sure the XP machine is sharing the directory you want to import and the user Dad with the same password and in the same group is on the XP machine.

Gerry

This worked perfectly! Thank you very much for the detailed response.

[waynedunham]

Originally Posted by gplasky

Right click on My Computer and go to Manage. Go to Services and find the SageTV service. Right click for Properties and choose the Log On tab. Put the user and password in "This Account". User must be an Administrator with a password. The SageTV Service Control exe is still in the SageTV directory. You can still use that. Also make sure you installed java on WHS. It's not done automatically on WHS when you install the SageTV Add-on thru the console.

Gerry

Perfect timing for this post! I'm just in the process of setting up a WHS Sage machine to replace my old tired P4 Sage machine.

I've got the WHS machine up and working, but haven't installed SageTv or ShowAnalyzer on it yet. Right now I've just got my old P4 machine saving all new recordings over to the new WHS machine so that when I do finally finish the migration it will go much easier.

Anyway.... A buddy of mine has been using WHS for his Sage machine for many months so I was asking him what user he had set up to run Sage/Sage Service and Comskip under.
He is just using "Local System". Now I migrated away from that on my existing machine using XP based on a lot of suggestions in the forums here.

For the life of me though, I can't recall WHY? I don't recall if it was to set Sage/Dirmon/Showanalyzer to be using the same user that my XP system automatically logs in as, or maybe another reason.

So why should I, or why shouldn't I, run Sage/Showanalyzer as "Local System" on a WHS machine?

Thanks

[gplasky]

Originally Posted by waynedunham

Perfect timing for this post! He is just using "Local System". Now I migrated away from that on my existing machine using XP based on a lot of suggestions in the forums here.

For the life of me though, I can't recall WHY? I don't recall if it was to set Sage/Dirmon/Showanalyzer to be using the same user that my XP system automatically logs in as, or maybe another reason.

So why should I, or why shouldn't I, run Sage/Showanalyzer as "Local System" on a WHS machine?

Thanks

So if you need to do the local loopback for something like the Netflix plugin, Slimplayer, etc you HAVE to do local system because it needs to interact with the desktop.

So if you have additional shares being used on additional machines you HAVE to use a user ID with a password that is in the Administrator group to run the SageTV service. That same user ID and password has to exist on the machine with the share that you want to use in SageTV.

That's why I have all of my storage on WHS. I can run as a local service and use the loopback workaround with no issues.

Gerry

[waynedunham]

Originally Posted by gplasky

So if you need to do the local loopback for something like the Netflix plugin, Slimplayer, etc you HAVE to do local system because it needs to interact with the desktop.

So if you have additional shares being used on additional machines you HAVE to use a user ID with a password that is in the Administrator group to run the SageTV service. That same user ID and password has to exist on the machine with the share that you want to use in SageTV.

That's why I have all of my storage on WHS. I can run as a local service and use the loopback workaround with no issues.

Gerry

Thanks, I think that answers my question. LocalHost it is.

[jahouse]

Has anyone tried using acronis disk director suite 10.0 for the "convert" method instead of the server version? It is only $49.99 instead of $499.

[voorhees]

OK, before I do something stupid, I thought I would ask the experts.

I have a WHS SageTV server up and running great. I have 3 drives; 1 for OS, and 2 in the data pool formatted with 64k clusters using the procedure outlined here (thanks S_M_E). I want to add a new drive to the pool. I have the new drive installed, but not in the pool. I was thinking I should reformat the drive with 64k clusters outside of the pool, and then add it to the pool. Is that all I need to do? Am I forgetting something?

Thanks so much for your help and guidance.

[wayner]

The instructions are posted here somewhere so try a search but I am pretty sure that adding the pool to the drive causes it to be reformatted. Therefore if I remember correctly you have to add it to the pool and then immediately go into Disk Manager and change to 64K.

[voorhees]

Originally Posted by wayner

The instructions are posted here somewhere so try a search but I am pretty sure that adding the pool to the drive causes it to be reformatted. Therefore if I remember correctly you have to add it to the pool and then immediately go into Disk Manager and change to 64K.

Great point. I totally forgot about that. I searched the thread several times but never stumbled up on it. I only found variations on the original conversion to WHS.

Do I need to make sure duplication is off on all shares before adding the new drive to ensure it does not try to put something on the new one before I get it reformatted?

Thanks.

[gplasky]

Originally Posted by voorhees

OK, before I do something stupid, I thought I would ask the experts.

I have a WHS SageTV server up and running great. I have 3 drives; 1 for OS, and 2 in the data pool formatted with 64k clusters using the procedure outlined here (thanks S_M_E). I want to add a new drive to the pool. I have the new drive installed, but not in the pool. I was thinking I should reformat the drive with 64k clusters outside of the pool, and then add it to the pool. Is that all I need to do? Am I forgetting something?

Thanks so much for your help and guidance.

Anytime you add a drive to the pool WHS will format it automatically and use 4k blocks. So don't bother formatting outside the pool. Open disk admin and MAKE SURE you know which one is the new drive. (Also use the WHS add-in DIsk Management to help) Bring it into the pool. Immediately go to Disk Admin and format with 64k blocks. Relax and let all drive activity settle down. (I usually reboot the server after it all settles down to make sure all is right with the world.)I have duplication turned off anyways but I would turn it off just in case. If you do it quick enough nothing's going to get on that drive.

Gerry

[wayner]

I don't think I worried about that and I don't think it will automatically rebalance to equalize usage across drives. Just add the new disk to the pool and once it is added then go in and change to 64k ASAP and you should be ok. I have 6 drives in my system - the system drive plus 5 data drives, and this is the way that I did it.

[gplasky]

If you turn off duplication and then add and format the drive and then turn duplication back on it should also help kick off the load balancing instead of leaving that drive empty for quite awhile.

Gerry

[btrcp2000]

I have had the parts for my new whs server for months, and it's going to rain all weekend, so here goes.

One question has me stumped. How vital is it to have the OS partition converted to 64k? I really have only seen the reference to it being "optional" from the first post of the tutorial, but nothing either way since. I currently have an empty whs server, no data drives at all awaiting the answer to this question in case I have to reinstall. TIA!

[Skirge01]

I don't think anyone has mentioned changing the C: drive to 64k, only the D: drive and any drives in the pool. There's no reason at all for the C: drive to be 64k.

[Skirge01]

Somewhat off topic, but I can't possibly be the only one wondering what ever happened to S_M_E. I know he wasn't the most popular person on the forums, but I'd never wish anything bad on someone.

Besides, he's the one who got this 64k revolution going.

[wit713]

I know this topic has not been posted in a while but I used these instructions back in September of 2009 when I originally built my WHS server to format my 2 data drives and the D drive to 64K.

I am finally running out of room on my data drives and I want to add some more new drives. Should I still format my new drives to 64K when adding them? My WHS drive has all the latest updates.

[-=Jeff=-]

Originally Posted by wit713

I know this topic has not been posted in a while but I used these instructions back in September of 2009 when I originally built my WHS server to format my 2 data drives and the D drive to 64K.

I am finally running out of room on my data drives and I want to add some more new drives. Should I still format my new drives to 64K when adding them? My WHS drive has all the latest updates.

I would.. all my drives are 64K in my WHS.. I did not read through this whole post again, but I remember the 64K helps when playing back video or such..

[gplasky]

Formatting to 64k doesn't hurt. And I still format any new drives I add to 64k just to keep them all consistent.

Gerry

[wit713]

Thanks for the advice