EyeOn Blog

ChannelWeb recently wrote an article about the changes that Solution Providers need to make to their business in order to successfully sell and service SaaS applications. It made me think of the paradigm shift that is required by our Solution Providers and how to communicate this to them and others.

It is not only a shift in what they are selling, but how they sell and service it as well. Professional Services, such as Configuration are new to them as opposed to programming and customization.

Software As A Service Means Big Changes

As a developer and ISV of a Windows Mobile-based solution, I am regularly connecting and disconnecting multiple devices to my workstations. I recently decided to upgrade my main laptop workstation that I use for most of my development, presentations, and everyday use to Windows Vista. While I have had little or no problems, including installation, configuration, networking, joining the domain, Active Directory, Visual Studio, etc a couple of things just would not work for me. The biggest headache had been the use of Windows Mobile Device Center, since Microsoft decided to scrap ActiveSync for WMDC in Vista. Will it connect or not, sometimes yes, sometimes no. After many hours of extensive investigation through logs, manuals, configuration files and research in the forums, I was finally able to boil this down to a security problem. Since my PC gets its Local Security Policy from the Domain Controller, there is no way to fix this locally. Apparently, Windows Vista is highly dependent locally on the ‘LOCAL SERVICE’ and ‘NETWORK SERVICE’ users to start and stop services, including Windows Firewall and of course WMDC. These users are not included in the Domain Security Policy, I do not know if this is normal or simply because my Domain Controller is an Windows 2000 Server box.

So here is what you need to do:

• Go to the Domain Controller box and login as Administrator
• Open the Domain Controller Security Policy
• Manually ad ‘LOCAL SERVICE’ and ‘NETWORK SERVICE’ to the following policies:
  • Act as part of the operating system
  • Adjust memory quotas for a process
  • Allow log on locally
  • Create global objects
  • Log on as a service
  • Replace a process level token
• Go back to your desktop and restart to refresh your Local Security Policy

You should be good to go. This worked for me, I can now connect all of my devices with Windows Mobile Device Center including Windows Mobile 2003, Windows Mobile 5, and Windows Mobile 6. This also starts the Windows Firewall, so the first time you connect it will ask you if you want it added as an exception to the Firewall rules.

Welcome to the new EyeOn Blog!

Please check back here often to get updated news and announcements regarding the EyeOn Data Management Service. This is a place for our partners and customers to find out what is going on at EyeOn and the future of our revolutionary, patented data mangement system.