These folders may have to be excluded from antivirus scanning when you use file-level antivirus software in SharePoint. If these folders are not excluded, you may see unexpected behavior. For example, you may receive “access denied” error messages when files are uploaded.
If Go Daddy is your DNS hosting provider, Office 365 can set up your domain for you automatically. Instead of going through all the manual steps, you can set up your domain with Office 365 in just a few minutes.
Differences between Office Web Apps (WAC) and Native Clients
It can be a little tough to discern the differences between the capabilities of Office Web Apps (WAC) and their fat-client counterparts in the desktop Office suite. While Microsoft doesn’t provide an outright comparison table, they do offer the following:
It is recommended to install June 2013 CU before SP2. June 2013 CU might not correctly identify the SP2 baseline. If SP2 has already been installed and June CU does not install you need to wait for August CU which will correctly identify the SP2 baseline.
Guess it wasn’t such a smart installer after all was it?
Let’s take a look at the version numbers based on installation order:
SP2 only - 14.0.7015.1000
June CU only - 14.0.7102.5004
SP2 then June CU - 14.0.7015.1000
June CU then SP2 - 14.0.7102.5004
Based on the original guidance from MS, you might be running the June 2013 CU baseline, but your build version will still show as SP2.
One of the frequently asked questions we get is “when will I get upgraded?” Some customers want to get upgraded as quickly as possible; other customers want more time to prepare. One thing that’s common is that every customer wants to know when they’ll get upgraded.
One important warning about changing the default sync folder: If you’re also syncing files using SkyDrive for Windows (the consumer version of SkyDrive), don’t use the same “root” folder to sync SharePoint libraries with SkyDrive Pro. The default root folder with SkyDrive for Windows is c:\users\[username]\skydrive.
So you’ve gone ahead and updated your Azure subscription to the latest billing model to take advantage of per-minute billing and no charge for stopped VMs? And now you’re still being charged for stopped VMs? As with all things Azure, there is Stopped and then there is
In Azure, all VMs are provisioned into the Fabric. When you stop a VM (either by shutting it down from within a RDP session or with the -StayProvisioned parameter of Stop-AzureVM) the resources assigned to your VM are left in place. This includes the VIP assigned to the Cloud Service your VM runs in as well as the dynamic DHCP lease assigned to it.
Taking a step back, now you’re thinking to yourself there is no such thing as a parameter called StayProvisioned on the Stop-AzureVM cmdlet. Well, what fun would it be if the product team kept the online documentation up-to-date? Let’s take a look at the cmdlet from a local PS session:
Get-Help Stop-AzureVM --detailed
Keeps the VM provisioned.
Accept pipeline input? false
Accept wildcard characters? false
OK. So if we shut a VM down from a RDP session or with the StayProvisioned parameter it sticks around. What if we shut it down from the management portal or we leave that parameter off?
We can see the status of our machine has transitioned to StoppedDeallocated. In this state, we’re no longer provisioned into the Azure Fabric and we’re not charged for compute resources.
Remember that stopping a VM isn’t always going to be enough to not be charged for compute resources. Also, keep in mind that if you stop a VM from a RDP session you can no longer issue a Shut Down command from the management portal so you’ll have to either restart it and shut it down from the portal or issue a Stop-AzureVM command.
Inconvenient Settings Loss With Dismount-SPContentDatabase
Are you someone that likes to go through your web applications and dismount your databases prior to patching? Or maybe you’re just moving a content database from one web application to another. Or maybe, just maybe, you want to dismount a content database for the fun of it!
Well, if that’s you, you might have noticed (or maybe not), that when the content database is remounted, a few properties get reset to their default values such as MaximumSiteCount and WarningSiteCount (2,000 and 5,000 respectively). This can be pretty inconvenient (to say the least!) if you’ve modified these settings in any way and even more inconvenient if you didn’t document them before running Dismount-SPContentDatabase.
Once again, it’s our friend PowerShell to the rescue. The following functions allow you to dismount all of the content databases in a given web application (Dismount-SPContentDatabases) while retaining the pertinent settings in CSV file. The function helpfully titled Mount-SPContentDatabases will remount the content databases (using Mount-SPContentDatabase) to the supplied web application using the previous settings (including the original DatabaseServer), thus saving you at least 5 minutes to enjoy an additional cup of coffee.
Imagine you have a web application with the name ContosoIntranet.
SharePoint 2013 Additional Prerequisites Unavailable for Download
As you’re all aware, SharePoint 2013 has some additional prerequisites that are required for a proper installation that aren’t included in the Prerequisite Installer. Todd Klindt just had a great post on this (so go there for the extra details), but he forgot to mention that 2 of the required hotfixes don’t currently have publicly available request forms. Todd was also nice enough to include some download links, so I’m posting them here as well for posterity.
KB 2759112 - A hotfix is available for the .NET Framework 4.5 that resolves an ASP.NET race condition issue in Windows Server 2008 R2 – Download
KB 2765317 - A hotfix is available for the .NET Framework 4.5 that resolves an ASP.NET race condition issue in Windows Server 2012 – Download
Coming in March 2013, following the release of the next version of Office 365, users will be presented with a streamlined sign-in experience. The sign-in page will a feature responsive design and was designed to “provide the best possible performance and experience on computing devices”.
If you’d like to opt-in earlier and test drive the new experience, click here.
Post opt-in, here’s what you’ll experience on the desktop.
You’ve been busy spinning up your RTM SharePoint 2013 farms haven’t you? And of course, you’ve been deploying under the least-privileged security model like any good IT Pro. After you have everything configured, you open the event viewer and what to your wondering eyes should appear? An error of course!
You’ve gone out and downloaded all of the perquisites for an offline SharePoint 2010 installation either by hand (or with a handy script) and you’re getting errors related to some of the files you downloaded? Yep, SharePoint is picky. For some reason or another the PrerequisiteInstaller really needs a super special version of the Microsoft SQL Server 2008 Analysis Services ADOMD.NET installer or else you end up with an error similar to the following:
Microsoft SQL Server 2008 Analysis Services ADOMD.NET: installation error
SPTechCon: Admin 2010 - So You're the New SharePoint Administrator...
It’s been a pleasure to attend and speak at SPTechconBoston 2012 with Dan Usher (@usher). Our first presentation was a 1/2 day workshop on SharePoint Administration for the new Site Collection Admin. Thanks again to all who attended.
Go placidly amidst the noise and haste, and remember what peace there may be in silence. As far as possible without surrender be on good terms with all persons. Speak your truth quietly and clearly; and listen to others, even the dull and the ignorant; they too have their story.
Avoid loud and aggressive persons, they are vexatious to the spirit. If you compare yourself with others, you may become vain or bitter; for always there will be greater and lesser persons than yourself.
Enjoy your achievements as well as your plans. Keep interested in your own career, however humble; it is a real possession in the changing fortunes of time.
Exercise caution in your business affairs; for the world is full of trickery. But let this not blind you to what virtue there is; many persons strive for high ideals; and everywhere life is full of heroism.
Be yourself. Especially, do not feign affection. Neither be cynical about love; for in the face of all aridity and disenchantment it is as perennial as the grass.
Take kindly the counsel of the years, gracefully surrendering the things of youth. Nurture strength of spirit to shield you in sudden misfortune. But do not distress yourself with dark imaginings. Many fears are born of fatigue and loneliness.
Beyond a wholesome discipline, be gentle with yourself. You are a child of the universe, no less than the trees and the stars; you have a right to be here.
And whether or not it is clear to you, no doubt the universe is unfolding as it should. Therefore be at peace with God, whatever you conceive Him to be, and whatever your labours and aspirations, in the noisy confusion of life keep peace with your soul. With all its shams, drudgery, and broken dreams, it is still a beautiful world. Be cheerful.
After a reboot, Dropbox on one of my Macs wasn’t playing very nice. From time to time, permission issues do crop up, but they’re usually due to storing your Dropbox on a file share or a non-native file system (e.g. FAT32) and my home directory is neither of those. This used to be a convoluted process that involved a trip to the command line, but it looks like the Dropbox team has added some hidden functionality to make this a breeze.
The Old Way
Run the following commands from a terminal window:
sudo chown -R $USER ~/Dropbox
sudo chmod -R u+rw ~/Dropbox
sudo chown -R $USER ~/.dropbox
sudo chmod -R u+rw ~/.dropbox
The New Way
Open the Preferences pane for Dropbox and:
Click the Account tab.
Hold down the Option key and the Unlink This Computer… button will become a Fix Permissions button.
Click the Fix Permissions button and quit Dropbox.
Apostrophes in Email Addresses with Exchange Online (Office 365)
There are several characters that can come off your keyboard that can make life with Office 365 a little painful, especially in a coexistence scenario. One such pain point is the use of special characters like an apostrophe (‘) in user principle names and email addresses. Please note that it is not possible to utilize an alias with an apostrophe in a non-coexistence scenario as the Exchange Online administration screens will not allow you to create the alias with illegal characters.
After the user has been properly configured, they will be able to send and receive messages via an alias that contains an apostrophe.
Office 365 Character Matrix
The following table details the special characters and their usage scenarios in Office 365 for user names, passwords, and email addresses (see Characters in passwords or user names in Office 365 for the original. I’ve added the email address column here).
* You can put a period or hyphen anywhere in your user name or email address except at the very beginning or at the very end. ** You can put an underscore anywhere in your user name, including at the very beginning or at the very end. *** Apostrophes can be used in non-primary email addresses (aliases) for both receiving and sending messages.
Configuring the Alias
Any user who wishes to make use of an email address with an apostrophe will need the additional addresses created within the source domain. A domain administrator or user with rights to update the Proxy-Addresses attribute within Active Directory should add the applicable aliases on behalf of the user.
For instance, if the user Demo O’Reilly (UPN firstname.lastname@example.org) wishes to have an additional alias provisioned for the address demo.o’email@example.com, an additional proxy address of smtp:demo.o’firstname.lastname@example.org should be applied to the user’s account in Active Directory. After the applicable proxy addresses have been applied, a Directory Synchronization (DirSync) should occur (either manually initiated or on the existing schedule) before the email address will be available for use in Exchange Online. After DirSync has completed, an Office 365 Exchange Administrator can verify that the alias has been applied to the user’s federated account.
Testing the Alias
After an Office 365 Exchange Administrator has verified that the alias has been created successfully, a test message should be sent to the user to verify that messages are being routed as intended. Note that the messages will be routed to the users primary email address (e.g. email@example.com).
Sign in to the Office 365 portal, and then in the header, click Outlook.
Click Options, and then click See All Options.
In the left navigation pane, click Account, and then click My Account. Under Account Information, click Settings for POP, IMAP, and SMTP access.
The Protocol Settings window lists the POP, IMAP, and SMTP settings for the user. Keep this window open or copy the settings information. You will need the information in the next step.
Configuring Outlook to Send Messages as the Alias
Open Outlook with the Office 365 profile.
Click File, then click Account Settings, and then click Account Settings.
On the E-mail tab, click New.
Click Manually configure server settings or additional server types, and then click Next.
Click Internet E-mail, and then click Next.
Enter the following information:
Your name: The user’s display name
E-mail Address: The alias that you want to send from.
Account Type: POP3
Incoming mail server: Use the POP setting that you obtained in Step 1. It should resemble pod#####.outlook.com.
Outgoing mail server (SMTP): Use the SMTP settings that you obtained from Step 1. It should be the same or similar to the POP3 setting.
User name: The user’s Office 365 sign-in name/email address.
Password: The user’s Office 365 password.
Click More Settings.
Click the Outgoing Server tab, and then click to select the My outgoing server (SMTP) requires authentication check box.
Click the Advanced tab, and then click to select the This server requires an encrypted connection (SSL) check box.
In the Outgoing server (SMTP) box, type 587.
In the Use the following type of encrypted connection list, click TLS.
Under Delivery, set the delivery options that you want.
Click Next. The account settings that you entered are tested. When these tests are completed, click Close.
A POP3 account is created for the alias. However, you also have to make sure that this POP3 account does not send and receive items in Outlook.
Making Sure the POP3 Account Does Not Send/Receive Items
In Outlook, click File, click Options, and then in the left navigation pane of the Outlook Options window, click Advanced.
Under Send and receive, click Send/Receive.
In the Group Name area, select All Accounts, and then click Edit.
In the Accounts list, select the new email alias account.
Click to clear the Include the selected account in this group check box.
Click OK, click Close, and then click OK.
Enable the From Field in Outlook To change whom the email messages are sent from (either from the user’s aliases or primary address), you may have to enable the From field in Outlook. To do this, follow these steps:
In Outlook, click New E-mail to open a new email message.
Click the Options tab. In the Show Fields group, click From to enable the From field in all new email messages.
Verify The Alias Can Send Messages in Outlook Send an email through the now configured “dummy” POP account to verify that messages are being routed as expected.
SharePoint Manager 2010 allows you explore the object model from your SharePoint servers, in some cases having the ability to make updates to system properties. Another great tool to keep in your toolbox.
A few additional Health Analyzer Rules to help your farm along with maintaining that red bar in Central Administration.
The SharePoint Health Analyzer Rules project is a collection of configurable SharePoint health analyzer rules that extends out of the box Health Analyzer system by adding many important additional rules that help to ensure your SharePoint environment is kept in optimal condition.