Sp1ForVs2010Managing i. Cal Calendar Sharing with Exchange 2. One of the new features available in Exchange 2. SP1 and higher including SP2 and SP3 that Im excited about and already making use of is the ability to share calendars from Exchange either in i. Calendar or HTML format. Microsoft. The fiercely competitive software giant is positioning its wares for cloud computing with software and services. The companys two cash cows operating. Welcome to Flight1. We have many great aviation products for FSXFS9 and P3D. Ive been given access to a server and told SP1 was installed on it, but I think maybe it wasnt. How can I check if Service Pack 1 is installed on Windows Server. In this article I go through stepbystep how to install MVC 4 in Visual Studio 2010. So why is this useful Doesnt Exchange 2. Calendar sharing with the new federated sharing features available from RTMWell, yes it does. And this new features doesnt replace federated sharing, however if you want to share calendars now is that the world doesnt run Exchange 2. Some organisations will move to it over the next year or two but lets face facts some enterprises out there may move to Google Apps, Zimbra or something else, so Federated Sharing isnt going to be an option. While a workaround might be to create partner mailboxes or use third party software, it would be nice to have a solution that just works and enables the business to collaborate with partners easily without worrying too much about what technology each other uses. Only with open standards can this happen and with SP1 thats now a reality. The ability to publish calendars with anonymous viewers and thats an important point, which Ill come back to means that should the admin enable it, the user can now go in via OWA, select the calendar they wish to share and choose to publish it. They then receive a set of URLs that they can share via email. The recipient then can simply refer to the calendar via a web browser, or by using any i. Calendar compliant software or web app they can subscribe to the shared Calendar. Getting back to the anonymous part, there are two options. The end user can publish a calendar with a public URL that is searchable. The other option is a restricted URL with an obfuscated URL. Additionally, the user can restrict what will be shown for each calendar they choose to publish. DataMgmt/vs2008sp1.png' alt='Sp1 For Vs 2010' title='Sp1 For Vs 2010' />On top of this, the admin can restrict via sharing policies the maximum amount of information users can publish, and sharing policies can be tied to a certain set of users. So there is some risk in enabling the facility, but by default no users calendars are shared, and there are a number of controls available to user and admin to pull the feature in line with the business and individual users requirements. Now you know a little more about the new feature, lets take a look at how it comes together from a user perspective, and how its configured by the admin. Hello,I have migrated an ASP. NET 1. 1 written with Visual Studio 2003 to ASP. NET 4. 0 Visual Studio 2010 SP1. The conversion of the VS 2003 solution was successfull. Add-SQL-CE-Item-To-ASP.NET-Project.png' alt='Sp1 For Vs 2010' title='Sp1 For Vs 2010' />The User Experience. If a feature is going to work well it has to be easy for a user to find and configure. Exchange 2. 01. 0 SP1 doesnt disappoint as the feature is listed in both OWA and Outlook in the same place as other calendar sharing options. For an OWA user, they select the calendar they want to share, then choose Share, and the option is listed as Publish This CalendarIf theyre using Outlook 2. Share and again, its listed as Publish This CalendarAfter clicking Publish This Calendar via OWA or Outlook, the options can be chosen including the detail to show, the date range and the type of access After clicking Start Publishing, the links are generated The user can now either copy the links from this page, or via Share choose Send Links to This Calendar which opens a new email with the two URLs attached. Opening the calendar by the recipient is easy enough. For our first example, lets have a look at Exchanges primary competitor, Google Apps. To add the shared calendar to Google Calendar, the end user chooses Add then Add by URL. They pop in the i. Calendar URL, and it shows up in the recipients Google Calendar. Youll see below Im subscribing to two Exchange 2. SP1 calendars my personal one and my teams In my case this is one aspect I personally like about the feature. Although I dont use Google Calendar I do use i. Google and it allows me to see my Exchange calendars on my homepage via the Google Calendar widget. Next up its Zimba. Add a new Calendar, choose Synchronise appointments from remote calendar, then pop in the Exchange i. Calendar URL Again, the Calendars show perfectly Finally lets not forget Outlook users from Outlook 2. Calendar subscriptions are supported. Ive quickly tried this in Outlook 2. Add Calendar and then select From InternetAs above, after popping the i. Calendar URLs in the subscriptions are created in the local Outlook client. And, finally lets not forget HTML sharing, which does exactly what youd expect The Admin Experience. Now youve seen the user experience lets take a look at what needs to be done to get it up and running in your SP1 environment. To get it all enabled we need to do the following Set an External. URL for your organisations Client Access Server. Enable Calendar Publishing on the OWA Virtual Directory. Create or modify the sharing policy to allow anonymous sharing. Setup of the External. URL is pretty standard stuff so I wont cover it here. Moving on to the Calendar Publishing OWA virtual directory feature, lets look at what its made up of. The Calendar Publishing works via a new virtual directory calendar. This lives beneath the owa virtual directory as owacalendar and has anonymous, http access enabled watch out ISATMG users. Its enabled by default but should it need re enabling its pretty straightforward using Powershell. Heres a quick example Set OWAVirtual. Directory owa Default Web Site Calendar. Publishing. Enabled true. Next up, a sharing policy needs to be configured to allow anonymous access. You can do this via EMS or via the EMC. The EMS example below changes the Default Sharing Policy to only allow anonymous access with maximum access level of Calendar Sharing with FreeBusy plus Subject, Location and Body. Set Sharing. Policy Identity Default Sharing Policy Domains Anonymous Calendar. Sharing. Free. Busy. ReviewerVia the EMC is also pretty straightforward and particularly suitable when you need to create multiple policies or modify existing ones. Heres a quick run through of how to create a new policy via EMC that only applies to certain users Open EMC and navigate to the Organizational Configuration node, then to Mailbox and select the Sharing Policies tab First, examine the sharing policies already present. Usb Video Audio Grabber. In the above screenshot, Ive got a single sharing policy which is disabled. As were adding a new policy right click in the white space or click New Sharing Policy on the actions pane. Give the policy a name and add a new domain called Anonymous and select an appropriate maximum level of access After youve added the domain anonymous to the policy, make sure its enabled, then press Next. On the next page youll be presented with the opportunity to add mailboxes now. You can of course add these later either via the EMC or via EMS Press Next, then after confirming the details, press New. After completion youll see a warning that lets you know calendar publishing is enabled for this policy Press Finish and were all done. You should now be able to login to the specific mailbox and following the first part of the article share the Calendar. Conclusion. Weve had a look at what the new feature brings both from an end user experience and to an administrator. As we can seen its great for sharing calendars in an environment where open standards are important or where partners use different products. Id like to see full Web. DAV compatibility so a Linux user can plug straight in and go, but this is a great start as far as sharing is concerned.