ASPHostCentral.com, the leader in ASP.NET and Windows Hosting Provider, proudly announces that we have supported the latest ASP.NET MVC 4.0 BETA Hosting.   

To support Microsoft ASP.NET MVC 4.0 BETA Framework, we gladly inform you that we provide this beta account FREE of charge for a limited time (* terms and conditions apply). 



New Features in ASP.NET MVC 4

This section describes features that have been introduced in the ASP.NET MVC 4: 
- Enhancements to Default Project Templates
- Better Support for Mobile Project Template
- Enhancement in Display Modes
- Mobile Project Template support for VB.NET
- Dependency Injection Improvements    

Terms and Conditions in Using this ASP.NET MVC 4.0 BETA Account 

The followings are the features you will get under this FREE ASP.NET MVC 4.0 BETA Account: 
- ASP.NET MVC 4.0 Beta Framework
- 1 Website/Domain
- 100 MB disk space
- 100 MB bandwidth
- 50 MB SQL 2008 space
- 24/7 FTP access
- Windows Server 2008 Platform

If you want to participate in this BETA program, there are several rules you need to understand: 

- As this is a beta version, not all the features are available. They may be some issues on this beta framework, which will be fixed upon the full release of ASP.NET MVC 4.0 Framework

- ASPHostCentral.com does not guarantee the uptime of the sandbox solution. Additionally, we do not keep/store any backup of your files/accounts

- ASPHostCentral.com does not guarantee rapid response to any inquiries raised by a user

- This free account is only meant for testing. Users should not use it to store a production, personal, e-commerce or any blog-related site

- This free account is used to host any ASP.NET MVC 4.0 beta website only. Any questions that are not related to ASP.NET MVC 4.0 BETA will not be responded. A user shall not host any non-ASP.NET MVC 4.0 site on this free account either

- ASPHostCentral.com reserves full rights to terminate this beta program at any time. We will provide a notification on our Help Desk System prior to the termination of this program

- ASPHostCentral.com reserves full rights to terminate a user account, in which we suspect that there is an abuse to our system

- Once this beta program is terminated, your account will be completely wiped/remove from our system.

- This offer expires on 31st May 2012

If you wish to participate in this FREE ASP.NET MVC 4.0 BETA Program, you must register via https://secure.asphostcentral.com/BetaOrder.aspx

ASPHostCentral.com, the leader in ASP.NET and Windows Hosting Provider, proudly announces that we will support ASP.NET 4.5 Hosting.

To support Microsoft ASP.NET 4.5 Beta Framework, we gladly inform you that we provide this beta account FREE of charge for a limited time (* terms and conditions apply).

The followings are the features you will get under this FREE ASP.NET 4.5 BETA Account:                

- .NET 4.5 Beta Framework
- 1 Website/Domain
- 100 MB disk space
- 100 MB bandwidth
- 50 MB SQL 2008 space
- 24/7 FTP access
- Windows Server 2008 Platform

 If you want to participate in this Beta program, there are several rules you need to understand:              

- As this is a beta version, not all the features are available. They may be some issues on this beta framework, which will be fixed upon the full release of ASP.NET 4.5 Framework
- ASPHostCentral.com does not guarantee the uptime of the sandbox solution. Additionally, we do not keep/store any backup of your files/accounts
- ASPHostCentral.com does not guarantee rapid response to any inquiries raised by a user
- This free account is only meant for testing. Users should not use it to store a production, personal, e-commerce or any blog-related site
- This free account is used to host any ASP.NET 4.5 beta website only. Any questions that are not related to ASP.NET 4.5 beta will not be responded. A user shall not host any non-ASP.NET 4.5 site on this free account either
- ASPHostCentral.com reserves full rights to terminate this beta program at any time. We will provide a notification on our Help Desk System prior to the termination of this program
- ASPHostCentral.com reserves full rights to terminate a user account, in which we suspect that there is an abuse to our system
- Once this beta program is terminated, your account will be completely wiped/remove from our system.
- For details, please check http://www.asphostcentral.com/ASPNET-45-Beta-Hosting.aspx
- This offer expires on 31st May 2012

If you want to participate on this FREE ASP.NET 4.5 Beta Program, you must register via https://secure.asphostcentral.com/BetaOrder.aspx

Problem definition

1. Our corporate email platform is Exchange Online, a MSCloud service. 
2. Our SharePoint (SP) servers are cloud based but are not hosted at a MSCloud service.
3. I need to setup SP to send automatic email notifications when changes occur. 
4. SP Administration allows the email notifications configuration only with SMTP servers set for Anonymous access.
5. Exchange Online provides an SMTP host but only works with authenticated access.

I can’t seem to successfully relay emails from SharePoint using the SMTP provided by Exchange Online.



Solution in a Nutshell 

1. SharePoint should use a local SMTP server.
2. The local SMTP server should be configured to relay to Exchange Online using authentication and correct ports.
3. Exchange Online should be configured to accept messages from your IP Range.

Before you go forward

1. The solution has been tested with: SharePoint Foundation 2010 and Windows Server 2008 R2 within a development environment.

1ST: Local SMTP & SharePoint

1. Open the Server Manager, I normally right click over “Computer” and select the “Manage” option.



2. Select “Features” on the Server Manager window and confirm that the SMTP Server is installed. If not select the “Add feature” option. I will assume you have it installed.



3. In order to configure the SMTP Server you will need to open the IIS 6.0 Manager. I know you are using IIS 7, butyou will be opening the IIS 6 Management Console (installed when installing the SMTP Server feature). Open it.



4. Right click on the Virtual Server and select “Properties”. There find the name of the Fully-qualified domain name.





5. Open the SharePoint Central Administration, go to the “System Settings” section and click on the “Configure outgoing email settings” link.



6. Fill the form using first the FQDN you found on the step 4 and then fill the email address you will use to send the notifications. This email is the one hosted on Exchange Online.



2ND: SMTP Server settings

1. Open the SMTP properties (like the step 4 above).
2. Be sure that the section of IP Address says (All unassigned) and then click the “Advanced” button. Confirm that the port is 25.





3. On the tab “Access” click on the “Relay” button and add the IP addresses used by your network interfaces. (An ipconfig command on the command prompt would help).



4. Click on the “Outbound security” button on the “Delivery” tab. Be sure to select “Basic Authentication” and provide the correct credentials for the account specified before on the SP Central Administration (step 5 above). Then select the “TLS encryption” box and Ok to accept the changes.



5. From the same “Delivery” tab click on the “Outbound connections…” button. There modify the TCP port to 587.



6. From the same “Delivery” tab click on the “Advanced” button.

-          There check that the FQDN is the same than the one set on your SMTP.

-          The smart host is set to: smtp.mail.microsoftonline.com. There is a list of other smart hosts available for different geographical areas.

-          Be sure that the “Attempt direct delivery before sending to smart host” check box is not marked.

3RD: Exchange Online should be ready to accept communications from your SMTP

1. Go to the admin.microsoftonline.com page and authenticate with your administrative credentials.



2. Select Exchange Online from the “Service Settings” tab.



3. On the “Safe senders” section you can add new Safe senders be specifying domains or IPs. In this case you should add the public IPs (normally one) that your SP box uses.



After all this is done I would advise you to restart the SMTP and IIS services.

Now you are free to start setting up some email notifications on your SP sites. Just be sure that your user accounts have email addresses assigned.

Hello, howdy? Today tutorial will explain how to upgrade SharePoint 2007 to SharePoint 2010.

Upgrade Steps

Run the Pre-Upgrade Check on the SharePoint 2007 Server

Execute the following command from the command line on the SharePoint 2007 server hosting the database to be upgraded:

stsadm –o preupgradecheck

This will scan the server for potential problems that may cause errors during the upgrade process.



Review the log file to get specifics on any issues.  The most likely cause will be features or customizations, so make sure that you uninstall any features or customizations that aren’t necessary on the new server.

Back Up Your 2007 Content Database

Back up your 2007 content database from SQL Management Studio on the SharePoint 2007 server, and put the backup file somewhere it is accessible from the new SharePoint 2010 Server instance.



Restore the 2007 Content Database to the SharePoint 2010 Database Instance

Connect to the SQL Server Instance hosting your SharePoint 2010 installation’s databases.  Restore the legacy content database from the backup file created in the step above.



Create a New SharePoint Web Application

Note:  If you have a Web Application created that you plan on using, skip this step and move onto the next step, “Detatch Any Content Databases from the Target Web Application”.

In Central Administration, select “Application Management” from the left navigation pane, and Manage Web Applications under the Web Applications heading.

Click the “New” button on the ribbon toolbar.



Under the “Database Name and Authentication” section, add “DELETETHIS” or something similar to the end of the database name to differentiate it.  We will be removing and deleting the generated content database.



Once completed, you should see the following success dialog:



Detach Any Content Databases from the Target Web Application

In Central Administration –> Application Management, select “Manage Content Databases” under the Database heading.

Select the target web application in the “Web Application” drop-down box at the top left, if it is not already selected.



Ensure there are no content databases for the target web application.  If the list contains any content databases, click on each content database name.  On the “Manage Content Database Settings” screen, select the “remove content database” checkbox and click OK.



Note: Make sure to log into your SharePoint 2010 SQL Server Instance at your convenience and delete any orphaned content databases that were removed from the web application in the step above.

Run The Powershell Test-SPContentDatabase Cmdlet

Launch the SharePoint 2010 Management Shell available under Start->Programs –> Microsoft SharePoint 2010 Products.  (Note: If running on a development/client instance on Windows 7 x64, ensure you launch the management console with administrative privileges by right clicking the icon and selecting “Run as administrator”).

Run the Test-SPContentDatabase command from the SharePoint 2010 Management Shell PowerShell window with the following syntax:

Test-SPContentDatabase –Name [DBName] –WebApplication [URL]



This tool will scan your Content DB and search for any references to Web Parts or Features that are missing on your SharePoint 2010 installation.  Each error will indicate whether or not it will block the upgrade, and gives a useful remedy for each issue.

Any issues not marked as Upgrade Blocking can be resolve post-upgrade. 

Restore the Content Database Using STSADM.EXE

Using the stsadm.exe tool, run the addcontentdb command using the syntax below:

stsadm –o addcontentdb –url [URL] –databasename [DBName]



Once executed, the command window will update with a progress indicator as seen in the screenshot above.  Once it is complete, you will either receive one of two messages:

Operation Completed Successfully

or

Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-[DateStamp]-[ids].log.  The number of errors and warnings is listed at the end of the upgrade log file.

You can also review the upgrade status in the Central Administration web application under Upgrade and Migration –> Check Upgrade Status.



This report contains the location of the log file for the upgrade process for future reference.

Review any upgrade errors and resolve before moving forward.

Accessing the Upgraded Site and Visual Upgrade

Accessing the Upgraded Site

Open a new web browser instance and navigate to the URL for the web application you upgraded.



You will notice the site retains the same SharePoint 2007 look and feel.  This was done deliberately to allow upgrading to SharePoint 2010 without introducing drastic interface changes to the client base. 

Optional: Visual Upgrade

SharePoint 2010 offers a simple method for upgrading the existing site to the new SharePoint 2010 look-and-feel. 

From the Site Actions menu at the top left, click “Visual Upgrade”.



From the “Site Settings –> Title Description and Icon” page, enter any site metadata you want to upgrade, and click the “Update the User Interface” radio button under the “Visual Upgrade” section as seen below.  Click “OK”.



You will now be returned back to your site’s main page with the updated SharePoint 2010 look-and-feel.

Problem

With evolution of search, different kinds of requirements arise for searching content. One of the requirements we came across was that they wanted to search for content from external locations (i.e. like Google, YouTube and other public facing internet applications).

Solution

SharePoint 2010 has a web part called "Federated Results". This searches content from the configured federated locations (like Google) that search content on provided parameters and generates output.

In this article, we will be concentrating on how to search content from such external applications. For this article, we will take "YouTube" as an external location. To define a federated (external) location, go to Central Administration > Application Management > Service Applications > Manage Service Applications > Search Service Applications. Click on "Federated Locations" under "Queries and Results" category.



Add a new location. We will first fill the general information: Location name (Youtube), display name (Youtube) and description (any suitable description) which makes a location unique.



Moving ahead to the Location Information category, we need to select the protocol which we will search content (i.e either Search index on the server, Fast index or opentext 1.0/1.1). For our requirement to define the YouTube location, we will select the Opentext protocol.

We also need to provide one mandatory detail which is the Query Template - which mentions from which location we will search and what will be the search parameter.

For our requirement we need to mention, "http://www.youtube.com/rss/tag/{searchTerms}.rss" where "searchTerms" will be the content searched in search box. Optionally, we can also provide a link for "More Results" that will appear at the bottom of search (as shown in the image below).

Leave the rest of the options to defaults.

Click on OK and add location.



Perform a full incremental crawl after the location is created.

Now go to the web application > search center results page and add a web part named "Federated Results" from "Search" Categories.



Edit the Web Part properties and browse to the Location section under Location Properties. If everything above is performed accurately, an option named "Youtube" will appear. Select it and apply changes.



Now we will search some content like "Microsoft" and we could see that with the search core results, a column of search results appears on right side of the screen which provides search results related to "microsoft" from youtube.



By implementing a process this way, it can reduce overburden of configuration and management of searching from federated locations.

We will now look at the setup required on our Exchange server to complete the task; this is the same in Exchange 2007 and Exchange 2010.

The first step is to create a new send connector so in Exchange Management Console navigate to Organization Configuration|Hub Transport and click the send connectors tab. In the actions pane on the right click “New send connector”


Enter a descriptive name and select internal from the dropdown list then click next on the next screen you will have to enter the FQDN’s of your SharePoint server.


Click next; on the next screen enter the IP address of your SharePoint server and make sure that Route mail through the following smart host radio button is selected.


Click next; the next page asks about your authentication settings leave this at the default “None” selection.


Click next; At Twynham we have all the Exchange roles on one Exchange box so the next screen asks for the address of the hub transport server which should be picked up automatically during the setup of the send connector but you can add one manually


Click next and then new and finish your send connector for SharePoint is now setup and we can continue to the next step.

We are working on a continuing SharePoint 2010 support project for a group of school one of the features they require is the ability for students to be able to have a drop box to submit their work to teachers, this is a perfect example of the use of mail enabled document libraries in SharePoint so I thought while I am writing this up I may as well share how to setup this function. This post will be divided into five parts:-

1)      Configuring SMTP on the SharePoint Servers
2)      Configuring Exchange 2010 to route mail to SharePoint
3)      Configuring Active Directory
4)      Configuring SharePoint 2010 Central Admin
5)      Document Library Configuration

Configuring the SMTP service on SharePoint 2010

The first step we need to do in the setup is to add and configure the SMTP service on one of our SharePoint web front end servers. I will be setting this up on a farm configuration with 2 web front end servers and 1 application server.

The SMTP service is vital for mail flowing into SharePoint so your first port of call is to log onto your chosen SharePoint server and open server manager and navigate to features here we can add the SMTP service



As you can see from the illustration below after the service is installed the server MAY require a restart in my case this was not needed but it may be needed on your server so please be aware that you may have to have some down time in your setup so plan accordingly.





As you can see from the illustration above the setup of the service is now complete and no restart was required. The next step is to configure the service through IIS manager on the server, for this you will need to use IIS manager 6 here at Twynham we install this role during the setup of our servers but you may not, if not installed open Server manager|Roles|Add Roles|IIS 6 Management Compatibility through this interface which you can see below we can manage SMTP



Right click on SMTP Virtual Server and choose properties once open click on the access tab and then click the Authentication button “Anonymous Access” should be ticked.



Next step click OK and then click the Connection button and ensure that “All except the list below” radio button is selected and click ok



The final button to click is the relay button and make sure that “Only the list below” radio button is selected and also make sure that you see a tick in “Allow all computers which successfully authenticate to relay regardless of the list above”



You can also fine tune the permissible message size by going into the messages tab this could be crucial for students sending in attachments via email so please make sure this is set to a reasonable limit.



You will find that all the settings are pre-set out of the box the only setting that you will really need to check is the Start-up type on the SMTP service by default this is set to manual so obviously change this to automatic

   

"A quick Note from the field is that I have found that if you restart your exchange server you will need to restart the SMTP service on your SharePoint servers, we route our internal mail from an ISA server to Exchange 2010 and this needs to be done after each restart of the Exchange box.” 

Starting from 7th Nov 2011, ASPHostCentral.com starts to offer a hosting service located in our prestigious Amsterdam (Netherland) Data Center. For further information, please click here.

For all our new customers who wish to have their sites activated on our Amsterdam (Netherland) data center, you must indicate your request on our order form at https://secure.asphostcentral.com. For our existing customers, a one-time migration fee applies to all requests on our Amsterdam (Netherland) data center and please creates a ticket from our Help Desk to signal your interest.

Our new data center in Amsterdam provides businesses across Europe region. The Amsterdam data center is complemented by new points of presence (PoPs) in Europe that will provide millions of new users with a direct, dedicated path to our Network, providing lower latency and a superior end user experience.

Network Details

Our global network seamlessly integrates three distinct and redundant network architectures—Public, Private, and Data Center to Data Center—into the industry’s first Network-Within-a-Network topology for maximum accessibility, security, and control.

We leverage best-in-class connectivity and technology to innovate industry-leading, fully automated solutions that empower enterprises with complete access, control, security, and scalability. With this insightful strategy and our peerless technical execution, we have created the truly virtual data center—and made traditional hosting and managed/unmanaged services obsolete.

We are proud of our high speed connection. In fact, one of our most frequent compliments from our customers is how fast their site loads... read on and you will see why. When you combine high speed connectivity and high quality equipment, you get a fast and reliable web site. We have invested in the equipment and staff so you can rest assured that your site will load fast every time. We host sites all over the world, and with our multiple backbone connections, your customers will get through to your site fast.

For more details, please visit ASPHostCentral.com website.

This morning I tried to upload a video file to our SharePoint 2010 install in preparation for a presentation tonight and then realised that the default 50mb file size limit was still set so while I was changing the settings to allow larger files I thought I would do a quick post on how/where the setting is and what to change.

First of all login to Central Admin and navigate to

Central Administration -> Application Management -> Manage Web Applications

Once there highlight the web application that you want to change and then click on general settings

Once in general settings scroll to the bottom of the list and you will see the maximum upload size the default setting is 50mb this can be can set to a maximum size of 2047mb. If you try to go beyond this it does flag up and tell you that you have exceeded the Maximum size.

The Sharepoint Designer has a lot of great features. While we won’t discuss every one of them here, we will take a look at some of the most noteworthy below. The reusable workflow, Designer ribbon, customized out-of the-box workflows and workflow action prompts, are the ones we will look at more in-depth.

1. Reusable workflow: This is a new feature, added since the 2007 version of the system was released. This particular feature makes it possible for individuals to create workflows that can be applied to as many libraries and/or lists as required by the company. The SharePoint Designer workflow settings page can be used to attach the reusable workflow to the library or list. Reusable workflow also makes it possible to forgo building a check content type action right into the workflow. This is one less step for IT and makes life a bit easier for everyone involved.

2. The Designer Ribbon: The Designer Ribbon provides the user access to many of the tools necessary to create workflows. Instead of having to pull up commonly used commands, one-by-one most can be found on the Sharepoint Designer Ribbon, making the workflow creator’s job much easier, significantly speeding up the development process.

3. Workflow action prompt: This prompt allows users to input their workflow logic into the workflow. The workflow action prompt will automatically make suggestions that match the information a person is inputting. This helps speed up the process and improves efficiency.

4. SharePoint Designer and Microsoft Visio Premium 2010 Import/Export: This is a brand new feature. It allows individuals to build workflows using Visio and also those exported into the Sharepoint Designer. Users will have access to every condition and action found within the Designer when they use the Microsoft SharePoint Workflow template found in the template section (Flowcharts) in Visio. If a person has already developed workflows in Sharepoint Designer, they can import them into Visio.

Sharepoint Designer is tool for creating workflows. Sharepoint has added a number of excellent features since the 2007 version. Though there are many, we’ve chosen to highlight only a few. Workflow action prompts, Two Way Import/Export of Sharepoint Designer and Microsoft Visio Premium, the Designer Ribbon and the Reusable workflow feature are just a few the new ones offered in the 2010 version of Sharepoint Designer, which weren’t in the 2007 version. For a comprehensive listing of features, individuals will want to visit the product’s homepage. There, individuals will find a complete listing of everything that’s included