As you may or may not be aware, Arno, Alex and I have been preparing the FSDeveloper.com face-lifted site for a while now.
The move is not only a face-lift and new logo, but a launch of new features and improved bandwidth capability. This is to allow for the fact that the ACES development team will be working more with the community on our site and that means the ability to cater for more users was needed. The good news is ownwebnow.com gave us a great deal on the hosting and we are essentially unlimited now with growth capacity!
So, come visit… and you too can work with like minded developers and the Microsoft ACES development team when they pop in! ACES members have the 
logo next to their name on the forum, and MVP’s have the 
logo – just in case you need to pick us out ;)
Come visit and tell your friends!
(Note that you will have to wait for the DNS to update to see the new site!)
As Arno has already mentioned on his blog, we did not get the move done this weekend for fsdeveloper.com, but this has been a bit of a blessing in disguise.
Because we could not move the databases due to technical issues, we decided to concentrate on the aesthetics of the new site. The problem is, Arno and I do not have a artist bone between us. So, I called in a favour from Alex Greenland, a very talented coder and web designer. He has, in 24 hours, given us a first draft of our new site and it is amazing! I can’t wait to get it uploaded.
Once the new fsdeveloper.com site is released, there will be a lot more promotion of our site as “the place to be” if you want to work with other like minded developers and the Microsoft ACES team developers directly.
It will just be a week later than expected.
Today, Netstreams Inc will be releasing an update to their Streaming Music Manager (SMM100) as part of their ongoing development of the DigiLinX product. This update comes as part of a much broader set of updates in the new DigiLinX Dealer Setup Program v2.0.
I have been testing the SMM100 since beta release on my own home network with Microsoft Windows Home Server and can confirm that all is working well.
After installing the update, the core improvements that are obvious are:
- Faster indexing
- Improved stability
- Playlist support! (.m3u files)
- Desktop client software that allows you to manage your SMM from a PC.
M3U
The first issue that I had to overcome was understanding the new .M3U playlist support. As I use iTunes on both a Mac and PC, I had to look for two seperate products to export playlists from both versions.
For the PC, I settled on Eric Daugherty’s iTunes Export
For the Mac, I used Bery Rinaldo’s excellent AppleScript
Both are easy to use, and once you have your .M3U file exported, you simply put the files in a location on your network that the SMM is already set to index.
Domains and Workgroups
For ages now, I have been running the SMM100 and had it set to index the “Media” share on my Small Business Server. The only issue with that is the SMM is not designed to be implemented in a “corporate domain”. (That said, it should be IMHO).
The only way I was able to get the SMM100 to work in this (domain) configuration was to allow the “Everyone” group have full permissions to the Media share on my server. This was not ideal for obvious reasons, especially the fact that the SMM attempts to logon to your DC multiple times using different methods continuiously causing security error on the server. This is why I decided to implement Windows Home Server, a product much better suited to this solution.
Windows Home Server works in a Workgroup configuration. It automatically sets up the Music, Video, Software, Users, Photo shares and then allows you to easily setup users to have specific permissions to folders. Do not worry, the Windows Home Server can exist beside your domain, and even prompts if your passwords are not syncronised on your domain and workgroup.
I configured an account for Rachel and I, plus a specific account for the SMM to use. The reason for this is (as I found out the hard way) if you use your own account on the SMM100 and then change your password, your entire music collection stops working! The netstreams user needs full permission to the Music share and nothing else on the Windows Home Server to be able to successfully index the resource.
Patience is your friend….
When I initially setup the Windows Home Server on the network, the SMM100 took a good hour to finally find the server on the network even though the IP settings send to the device were perfect.
My point is that if you are implementing the SMM100 in this configuration, be sure of the following things, and then wait at least an hour for the resource to become “Online” in the new desktop client:
- Check that using dealer setup, the username and password you setup for your Server / PC is exactly the same.
- Do NOT use DOMAINNAME\Username format, it is not supported. Just use the Username.
- Be 100% certain that the SMM100 is in the same subnet as the PC’s you wish to index. (i.e. if your Windows Home Server is in 255.255.255.0, so must the SMM100).
- After rebooting the SMM100, ensure that the Dealer setup changes to a “Green tick” and does not remain on the “Yellow caution” sign.
- After rebooting the SMM100, wait… then wait again… then go and get a cup of tea… do a bit more waiting… then look at the desktop client and see if it is indexing.
Here is a screenshot of the new desktop client. So far I have not managed to get it working on a Vista machine on my domain. I have only managed to get it working on XP and Windows 2003 Server. This may be a domain configuration issue, or just a currently unfixed bug. Either way, run on XP or 2003 for the moment.
As you can see from the image above, all network resources have been found on the network. However, I have the SMM set to only scan for sharenames that contain the word “music”, therefore only the music share is showing as “Active”. The status is showing as Online, which means that the SMM100 can see the server and share on the network. If music in that share changes, you will see “Scanning” instead of “Online”. This simply means that it is scanning the folders changes. If you screen looks the same, all is good…
SMM100 and Windows Home Server ongoing…
As you can see from above, these two products marry well on a home network. However, I feel that somehow something is missing. Sometimes I wish I had learnt to code so I could do this stuff myself, but in the mean time if you are a willing developer, may I suggest the following ideas for a Windows Home Server Add-in:
- Give us the new SMM100 desktop client information on a Windows Home Server internal webpage. This way it can be monitored on a secure website internally and remotely!
- Give us a hosted version of the netstreams dealer setup application (it’s written in flash, so it could not be that difficult – could it?)
- Give us a webpage on the Windows Home Server that displays the same as a TouchLinX. Again, it’s already a flash application, so it should work easily.
Knowing the way that both the Netstreams and Microsoft teams for these products are very passionate and forward looking bunches, I do hope that they can put their heads together on this!
Some of you may be interested in Herman’s blogpost on Netstreams Incorporated first 5 years in business.
For me, every time I work with Netstreams product, I am amazed as to how such a young company can produce such outstanding systems. I look forward to selling more and more of this product in the Irish market, so here is to the next 5 years! 
As many of you know, I admin my friend Mark Minasi’s technical forum.
For the past few years the Minasi Forum Meeting has been growing and growing and has become a great event to be at! The registration is now open for the 2008 event.
Due to current life pressure I am still unsure if I will be attending, but if I do, I will probably give some “over lunchtime” presentation on SBS or WHS….
Here are the details you need:
I would also like to thank Eric Rux personally whom has been organising this whole thing along with other forum members!
An annoying error at the best of times, and normally related to actual permissions problems in the registry, the file system (spool directory) permissions, or a problem in the driver itself.
But, and this is the hard information to find until this blogpost becomes more Googable, this problem can also happen with newer printer drivers on non NTFS PC’s. In other words, converting from FAT32 to NTFS is all you need to do to fix the issue.
convert c: /fs:ntfs
I am a long time user of SnagIt, and have been testing some of these new accessories for a while now. I thought it worth a mention that the following
SnagIt Outputs are now available for download.