Anith Gopal

The HealthVault Application Configuration Center is available at https://config.healthvault-ppe.com .  You login to this tool with a HealthVault-PPE account and it will show you a list of ApplicationIds for which you have admin rights.  Generally you will see zero or one ApplicationIds in this list.  Here is the home screen that I see with one of my Microsoft accounts: There are three ways for an application to get onto your list: Create AppId in Application Manager client: when Application Manager uploads your ApplicationId information to the HealthVault-PPE platform, you will be prompted to login to the Application Configuration Center.  The account with which you login will become the admin account for this AppId. Create AppId in Application Configuration Center: there is a “Create a new application” link in the screenshot above.  If you use that link to create an AppId then the currently-logged-in account will be the admin for that AppId. Submit a request: if you don’t remember which account is your admin account, if you lost credentials to an admin account or if your ApplicationId was created before the existence of the Application Configuration Center then you can “reclaim” admin rights to your AppId by clicking the “submit a request” link on this page.  You will see the dialog box below.  Enter the AppId that you want to reclaim and the email address where you would like to receive the reclaim invitation.  A Microsoft person will review your request and verify that it is coming from a company that is associated with the application, then they will send the invitation mail to the specified email address

An often-requested feature for VSTO add-ins is the ability to install an add-in for all users of a machine.

With all the improvements in SharePoint 2010 for IT Professionals, I always put Windows PowerShell support as the number one. Maybe this has something to do with my past Linux/Unix background, but the main reason is, I’m a really really lazy person. If something can be put into automation, then why bother to click through it manually every time

One of the themes from the UCISA conference this year, from the first keynote on, was the possibility of massive upheaval in the higher education sector in the UK. Tough spending reviews, new ways of doing things and the very imminent possibility of multiple mergers and acquisitions between universities in the UK.

In my previous post, I noted that rustock had started sending us a whole pile of spam over the TLS protocol.  The question now is why do it at all?  I mentioned in my post that this is clever behavior and one of my readers posted in a comment “What makes this so clever?” The issue of authentication, reputation and security is one that comes round and round in the world of email.  Why do we authenticate?  And what does it buy you?  There are plenty of reasons to send authenticated mail, here are three: It allows you to track abusive behavior. If an organization is sending outbound spam, then determining who is responsible for it allows that organization to track down who is sending it and shut them down.  This, of course, presumes that organizations want to do the right thing.  But if you are taking responsibility for the quality of what you send, then identification of your users is done using authentication. It allows you to combat fraud.