Yeah, me too! It happens when you actually setup two accounts in Outlook 2010 to connect to Office 365 outlook.com servers. It does NOT happen if you open a second mailbox under the first primary one, but less people do that on Outlook 2010.
Apparently the fix is coming in Office 365 when they upgrade the servers to Exchange 2010 SP2, but I have heard that even then this may not work. The guys on @Office365 twitter account are aware of this, and I have a case open on it they are directly referring to.
The fix I stole from this thread (Brendan Erofeev thanks!), but I wanted to make it a bit clearer.
Essentially, the problem is that the Windows Credential manager is unable to save credentials for two Microsoft Outlook configured proxies. That means that one of your accounts will always prompt you and become disconnected in Outlook. The hack, until Microsoft fix this is as simple as creating a hosts entry to the same IP of your servers proxy and setting that in Outlook. Here is a step by step:
- Open Outlook. Click File, Account Settings, Account Settings….
- Double click on the first account, click on more settings, the Connection Tab, then Exchange Proxy Settings Button. Write down the server name in the “Use this URL to my proxy server for Exchange:“
- Cancel out of the above account. Keep note of the proxy server you just wrote down. Lets pretend yours is msprd001.outlook.com (it will be different than this!).
- Next open up your hosts file on your PC. (If you need to know where this is, click here).
- Open up a Command Prompt on your PC. Type nslookup msprd001.outlook.com and you will be given back an IP address for this server. (Obviously, replace the server name above with the one YOU wrote down earlier). Take note of this IP. Lets pretend its 18.104.22.168 – again, it wont be, this is just pretend ;)
- Now, in your hosts file, add a line that says (remember, use YOUR IP you wrote down):
and another entry
(The 127 address is so that Outlook does not rediscover the corrected settings again from Microsoft).
- Pause for a moment, and take in what we are doing here…. We are creating a false and spoof DNS name “spoofproxy.outlook.com” for the same IP address of your actual servers proxy. This will mean we can use this proxy in the second account in outlook and Windows will save your password and all will work properly.
- So, again, follow the pretty path in the image I spent hours creating on step 2 above…. but this time do it on the second office365 account in outlook. When you get to the last step of the arrows, you change the name there, and only there, to spoofproxy.outlook.com
- Lastly, and importantly, you need to add a loopback IP for autodiscover to the hosts file.
- If you followed this correctly, you should now restart outlook and have two working accounts.
If your computer self combusts, explodes or in some other way disintegrates, you cannot hold me or anyone at NTES responsible!
Most people say that I act like a child.... but Microsoft always make me come over all excited when I hear about beta releases of Microsoft Flight (Simulator).
I have to say, it seems like only yesterday I was ranting at the MVP summit to Steve Balmer about the companies decision to axe the team making Flight Simulator, so many people loved the product. It has also been an odd one from a MVP perspective, because soon after (the year after this picture was taken) they got rid of all the Games for Windows MVP's. This, I thought odd considering they had announced then that they were "working on a new project" which we now know as Microsoft Flight.
Since then, its been lockdown! I can only presume there is some really big reason for that... My simple guess is that the team working on the product did not from one month to the next if they would be kept and they didn't want to announce or show anything without knowing for sure it was going to happen this time. (FSX was a marketing disaster on this front).
I also worry that there will never again be Games for Windows MVP's. This is of no direct concern to me, as I of course am a Small Business Server MVP and am in my 10th year in the program. But I do hope that they engage with MVP potentials around the globe again after the product is released as it would be a shame not to have that two way interaction with the team and the "end user" ongoing. I do note that this year's MVP summit has no events planned or product representation from the Games for Windows teams.... its a shame.
Anyway, we must push those thoughts aside... if I keep going on, I might not be accepted to the beta! That would be a disaster!
Oooooooooh, I can't wait!
I had meant to copy this over to my blog last week! We have had a few sites with this issue, so the more people with this information the better. Taken straight from The Official SBS Blog.
Issue Description and Symptoms:
Last Tuesday (9/13/2011), KB2494001 “MS11-074: Description of the security update for Microsoft SharePoint Foundation 2010: September 13, 2011” was released to Microsoft Update.
By default, the update will be automatically approved for installation on SBS 2011 Standard. However it will still require administrative action to be installed.
As with all SharePoint Foundation 2010 updates, you must complete the update process by running psconfig after the update is installed. If your server is not yet running SP1 for Windows SharePoint Foundation and you do not run psconfig after installing this update you may encounter the issues described in http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx. The most common issue is that SBS backups start failing.
The symptoms and behavior are described here in more detail:
To resolve this issue you must run psconfig as described in this blog:
- Open an Administrative command prompt.
- Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
- Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
SBS 2011 Standard UR1 Improvement:
Since Windows SharePoint Foundation 2011, included in SBS 2011 Standard, is the first version that requires psconfig to be launched manually we expect that this is an issue that will linger for the foreseeable future.
To address this issue we have introduced a new feature in SBS 2011 UR1. SBS 2011 Standard Rollup Update 1 was released yesterday (9/15/2011) and when installed, it adds warnings in the console and the desktop that will help identify this situation and provide documentation on how to recover.
After installing the rollup, a new scheduled task will be created; this task is set to run every day at 1:15am.
This task scans the event logs to see if the SharePoint Health Monitor that is scheduled to run at 12:00am has detected a situation that requires the databases to be upgraded using psconfig.
When the issue is detected, a Domain Wide group policy that is created by the UR is enabled to show the message on logon to any Domain Admin login on to any domain workstation. When is no longer detected, the User configuration settings are disabled.
When the issue is active, this is what a domain administrator will see when logging on:
Note: this message will only be cleared after the issue is resolved and the schedule task runs again that night. If needed, you can re-run the scheduled task in Task Manager, under Microsoft\Windows\Windows Small Business Server 2011 Standard.
The task writes a log called WSSPsconfigurationNotification.log in C:\Program Files\Windows Small Business Server\logs.
We also have the more traditional console alert, if configured, an email will be sent when this alert is detected.
The alerts point to Kb2580174 Receiving SharePoint Health Analyzer alerts in SBS 2011 Standard
Today we were setting up a customer with SBS Essentials. They had a few XP machines that needed to join the SBS Essentials network.
Oddly, they failed after they joined the domain, but tried to install the client connector software.
On looking in the logs in:
C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs
I found this line:
ClientSetup: Could not ensure NetTcpPortSharing service is Running:
I then checked the services and sure enough the .NET framework 4 service had completely hung. Killing the service did nothing and restarting also failed.
Eventually, I ended up having to use a completely horrible and unsupported fix…. which was as follows:
Kill the service:
Then go into:
C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation
Copy SMSSvcHost.exe and SMSSvcHost.exe.config from that location.
Then go to:
Backup the two files above mentioned in THIS folder (or rename). Then copy the files from above to here. The service that is hanging will then start correctly.
Then, your Connect computer wizard will run perfectly!
I had a customer today report that when loading Microsoft Excel 2003 the machine kept prompting for the SKU1CA.CAB file.
That pointed me to this article, which turned out to be a dead end….
The answer, in fact, was to go into the registry of the local machine and browse to:
In here, I changed the CDCache from 2 to 0
On reload of Excel, all was fixed!
Much fanfare, party hats, whistles….. massive advertising…..
Office 365 is here…. but is it?
Right now, as I type this I am on the phone to Microsoft Online Services technical support whom obviously have had completely ZERO, nil, nada training in BPOS to Office 365 migrations. Worse, they are obviously embarrassed about it.
Simple example… I have a small customer of 20 users on BPOS. They want on Office 365 now, and I am trying to initiate the migration request. Reading this page linked directly from Microsoft's own transition pages…
Sign in to the Office 365 portal using the same credentials you used in BPOS and then see Set up your desktop for Office 365. For information about using Lync 2010, see these Lync quick start guides and the Lync section of the Getting started page.
Really? Well I have tried this now with three sets of BPOS user admin accounts and guess what…. you can't logon. Worse, the technical support team don't know why, nor understand that instruction.
I thought then that I might be missing some step, so went back to the Administrator instructions linked from the same Microsoft transition pages where I read this:
For each subscription that you have, make sure that contact details for both the account owner and service administrator are up-to-date.
Monitor these email addresses regularly to check for email communications about transition.
Add @email.microsoftonline.com to your safe senders list to make sure you receive communications from Microsoft Online Services.
Ummm.. ok? What exactly does this mean? I am the admin, and do already monitor these addresses. I am beginning to think that, in fact, Office 365 isn't quite as ready as Microsoft would have you believe for BPOS customers.
Bit of a #FAIL and very unclear as to what we have to do to initiate our customers migrations. Please fix it Microsoft.
...especially considering the client the OEM products are aimed at.
Over this holiday, I have helped my Mum setup a new home PC. Two full days I have been at it. Its not that it would not have worked out of the box, but it would have simply not been "right".
Firstly, the computer is an excellent one apart from this stupidity by the OEM partner (in this case Sony). The same problem also exists on the equivalent Lenovo so I am not picking out one particular vendor. This computer is one of the new All in one touch screen systems. Like I said, pretty impressive apart from this annoying need for vendors to install crapware. Some examples of what I have had to do, and my Mum should not be expected to do!:
- Figure out that Sony had completely disabled Internet Explorer as the default browser and installed Chrome. Reinstalling IE9 and setting defaults was not enough, I had to make registry changes! Not good!
- See that Sony had installed a load of bloatware applications that were scanning for media completely inefficiently and slowing the fast system to a crawl.
- MY MAIN GRIPE: See that not only had Sony not provided Recovery media (they want 50 Pounds for that here in the UK where I am staying), but they had deliberately NOT put the software on the system that creates the recovery media! That is awful for an amateur user!. I had to go to the Sony site, download a thing called Sony VAIO care and then update that again, then create the recovery media. Terrible!
Rant over! For now! ;)
Today I noticed that a lot of upgraded SBS 2011 Sites (from migrated 2008 and 2003) that we come across have a lot of old group policy settings. I therefore thought it might be helpful for some of you SBS admins to have this information to hand. These are the default SBS2011 Group Policy settings.... if you spot any mistakes, drop me a line and I will update.
Windows SBS Client - Windows XP
select * from Win32_OperatingSystem Where (Version>='5.1.2600' and '6.0.6000'>Version and ServicePackMajorVersion>=3) or (Version>='5.2.3790' and '6.0.6000'>Version and ServicePackMajorVersion>=2)
Windows SBS Client - Windows 7 and Windows Vista
select * from Win32_OperatingSystem Where Version>='6.0.6002'
Windows SBS Client
select * from Win32_OperatingSystem Where ProductType!=2
Group Policy Objects on Default SBS2011 Install
Default Domain Controllers Policy
Default Domain Policy
Small Business Server Folder Redirection Policy
Update Services Client Computers Policy
Update Services Common Settings Policy
Update Services Server Computers Policy
Windows SBS Client - Windows 7 and Windows Vista Policy
Windows SBS Client - Windows XP Policy
Windows SBS Client Policy
Windows SBS CSE Policy
Windows SBS User Policy
Anything outside of the above is non-standard and may well be causing you issues on your new SBS2011 Domain! The most common issue we have found is update services issues.
Well, by now you have probably had this problem if you are reading this. Windows 7 SP1 is crashing on bootup on Dell, HP and Acer OEM installs of Windows.
This is a terrible problem, and I am not sure if I blame HP, Dell, Acer or Microsoft. But I can say this…. Microsoft are the only ones being helpful! I was working with them last night in America and they are putting some serious effort into helping users with this problem.
The method I was using until yesterday evening was to edit the pending.xml file , but in all cases I have had this has caused the machine to boot back, but it seems to be in a sort of no mans land between SP0 and SP1. I suggest strongly NOT doing the method mentioned where you edit the Pending.xml file! (here is the method if you REALLY must)
The methods I suggest are documented here, but I will put them below as well…
Note that on all machines I tried, the System restore did not work.
Option 1 (Win7 client only): Use a system restore point to recover the system
- This one is pretty self explanatory. Boot your machine into WinRE and pick a restore point before the service pack was installed. This should get you back up and running.
- This doesnt work on server
Option 2 (Win7 client and 2008 R2 server): Delete the poqexec entry
- Boot into WinRE and choose a command prompt then run the following commands and restart the computer:
- Reg load HKLM\BaseSystem C:\Windows\System32\config\SYSTEM
- Reg Delete "HKLM\BaseSystem\CurrentControlSet\Control\Session Manager" /v SetupExecute
- Reg add "HKLM\BaseSystem\CurrentControlSet\Control\Session Manager" /v SetupExecute /t REG_MULTI_SZ
- Reg unload HKLM\BaseSystem
This is the method I suggest as the easiest!
- If you're more graphically inclined, you can use this method:
- Boot into WinRE
- Open Registry Editor using regedit.exe
- Now you will have the WinRE registry loaded so you need to load the “ System ” hive
- To do that : Highlight HKLM then Click on File > Load Hive > Browse to C:\windows\system32\config (assuming C:\ being the system drive )
- Name the Hive as TEST
- Browse to HKLM\TEST\select and check the value for “ Current “
- Assuming the value as (1) browse to HKLM\TEST\ControlSet001\Control\SessionManager
- Locate and double click the key “SetupExecute ” at the right panel
- Delete any value inside the key and click OK
- Highlight TEST and then Click on File > Unload hive
- Type exit at cmd
- Reboot the machine
OK, this isn't listed anywhere on GFI's website, and until it is, at least you can find the info here.
If you have a firewall policy in place restricting internet access but still want to allow the GFIMAX agent to run, you need to allow access to:
Well, the time has come…. our office has been testing the latest beta version of Small Business Server (V7) and I am about to embark on the migration (Microsoft’s method, not Swing migration) to the RTM code.
Here are my notes, as it happens….. I am reading a RC version of Microsoft migration document.
Source Server Prep….
I am running on HyperV (My server is virtualised). I have taken a backup of the VHD file so that if all hell breaks loose I can roll back to this. I am shutting everyone off the network.
I am running some Line of Business applications, and other third party apps… I am noting these as I will need to reinstall them (GFI Mailarchiver is the main one I need to look out for).
I have put the SBS 2011 CD in the server, I am running the preparation wizard that Microsoft have supplied, this takes me through a few steps, including creating an answer file which I will need for the new server to join this existing domain. Check, done….
Time to complete – 30 minutes, plus some while the VHD file backed up…
New Server initial prep
I have created a new Virtual Server, and I have set it up to boot from the SBS2011 DVD with a Disk with my answerfile on it which I created earlier (in true Blue Peter fashion).
Boot the box, start the installation…..
Run through the custom install, answer the questions…. wait for about three hours while it installs everything and joins the domain.
Fall asleep at computer – check, Wake up with the worst pins and needles, try to walk, fall over and lay in middle of office for 10 minutes – check.
Go home to finalise migration.
Total time – 3.5 hours, 10 minutes on floor.
On arrival at home, noted that wife complained to me that iPhone had insisted on her having to type in a PIN to access the exchange server. This is slightly odd as I have not migrated anything yet. Suspect that this is simply a policy that the new Exchange Server being added has caused.
Redirected folders. Thankfully we do not use them any more, and I am glad of it… Redirected folders are a pain in the ass and we don't recommend them to anyone anymore. This means I can skip over this section of my migration. Though the documents give full details if you have to.
Turning off UAC (user Account Control) on the server. Another pain in the hole… I hate as an admin having to approve everything I want to do multiple times! Gaaaaaaah
Migration steps are asking me to reconfigure the network with the connect to the internet wizard. This scares me slightly as I am not sure if it will kill off my existing connections to the office. Sure enough, the wizard fails and my SMTP connectors in Exchange which I always modify to secure down the server are to blame. The SBS Fix my network wizard seems to fix, but will need me to look more at it later…
OK, moved over the Certificate from one server to the next… that part was easy.
The bit that always destroys everyones migration. My Internet address wizard is now working since I imported the cert, so that is one thing out of the way.
The documentation is telling me to setup my smarthost, done… but it is also telling me to remove my inbound SMTP connector (which is then routing the mail to the new server internally). I am going to leave that in place for the moment as I cannot get to the router to configure the change in inbound SMTP ports… later…
No POP 3 connector for me to migrate. Skipping that.
Next, started the move of the Public folders over after creating a new Exchange 2010 public folder. My Source Beta server is SBS01, the new one is SBS. I used these two commands…. the first gives me a set of stats on the Public folders to compare to later… the second moves the replicas.
Get-PublicFolderStatistics –server SBS01 | fl | out-file C:\Users\sbsadmin\Documents\PFSBS01stat.txt
.\MoveAllReplicas.ps1 –Server SBS01 –NewServer SBS
I now have to wait up to 24 hours for the replication to move…. The command I will use to then get a new text output to compare to the first one above is:
Get-PublicFolderStatistics –server SBS | fl | out-file C:\Users\sbsadmin\Documents\PFSBSstat.txt
I’ll come back to this later to set the default public folder DB to be that on the new server, then remove the other one…
More Exchange Migration
Move the Default Offline Address book – done, nice and easy. Change the Web Based distribution server to the new one, also easy. Lastly, set the default OAB for the new MailBox database. Done!
Now I can kick off a mailbox move request (local) for all the Mailboxes on our server. This will take a while, maybe overnight. So, on that note, I am going to bed….
My recording the next morning shows it took my store 3 hours to move. But this could change of course dependant on specific sites.
Turned on the circular logging on the new DB.
The backup of the database was easy, but restoring had a few gotcha’s that you should look out for. First, the instructions did not give me in big red writing the fact that I had to run the SQL Management studio “as administrator” It was bold, but I missed it a few times. So, lesson learned people RUN AS ADMINISTRATOR to be able to restore the DB.
Second, I had to run a command to mount the restored DB as http://companyweb. The same issue occurred and I had to give SBSAdmin user the full permissions to the database to get this to work. Another one for the notebook!
Updates Updates Updates
This is a brand new product, and I have 36 critical updates and 20 optional. That is an annoyance!
1.5 Hours (Wasted!)
Copy of file shares and user folders
Another easy, but time consuming step. All went well using robocopy.
3 Hours – 58GB.
I am now live running SBS 2011! Yay me, well worth the overnight migration.
Lets hope the staff can function tomorrow : )
Well, the time is nearly here. Small Business Server 2011 is soon to be released to the masses, so start reading up here:
Via Susan Bradley
No point in posting the video twice
Well, I was going to do a fanfare and a great big long blogpost…. but since we have just had Twins added to the Whittome family I am going to use that as the best excuse ever to simply link to the official post over on the Official SBS Blog!
You should note the new Essentials edition, which is an obvious push by Microsoft to the cloud. Not a bad thing! Something that NTES have been doing for a couple of years now for our clients, so this product will be fantastic for our new and current client base.
Yay! SBS 2011….
I really do not know what it is about the Sage Management and their underlying development team, but they never seem to finish anything! I remember years ago when I was working for a Sage Solutions Centre in Dublin they must have tried to release a windows version of Sage Soverign (which later got named Line 100) about 5 times and always failed.
Then they told everyone about three years ago that they were working on a version of Sage 50 that used MySQL Database…. finally we all thought! A version of Sage 50 that will actually NETWORK properly! Gah! I KNEW it was too good to be true.
I got a copy of this announcement today. Unbelievable…. I think it must be time to look at an alternative product now for us and our customers. The underlying Sage 50 (essentially flat file DOS format) data HAS to go, and QUICK!
Major FAIL from Sage…..
But it sure reminds me of the excitement it generates when snippet videos are released. Unfortunately also I am not going to make it to this years MVP summit :( That means that bribes and whisky won’t work this year.
The Microsoft Flight Team over at Microsoft have updated the site again, and put up another video. Check it out.
Over the past couple of days (i’m behind I know!) Clearone Netstreams have released a bunch of cool stuff. Its worth a blog post as some of this is a major change for the system.
First! There is a completely overhauled and improved website – www.netstreams.com – which gives you a far better feel for the systems from Clearone Netstreams.
Next, the announcement of the iPod dock. This will be cool, as we have been having to use the iPort with a MediaLinX device to achieve the same for our business and home users which was a pain. Being able to have a device that simply connects to the DigiLinX network and allow people visiting our customers homes and businesses to simply dock and then have their music shared and indexed will be AWESOME!
Lastly, but not least. Anthology is a product that (quoted from the site.)
“automatically scans for music stored on network attached storage devices and on PC’s. In addition to monitoring shared folders on PC’s and networked storage devices, Anthology also monitors its USB ports for USB storage devices that contain audio files, including iPods.
Internet Radio: Stream music to any room in your house. The Anthology can tune into thousands of stations of music, news, talk radio, sports. Streaming interned radio, your personal audio files or online services like Pandora, SIRIUS has never been this easy.”
All in all, this is good news from the Clearone Netstreams team, its great to see this product growing and advancing.
NTES, as an authorised Netstreams Dealer in Ireland, will assist customers with any questions on the above products and existing ones alike! – http://www.ntes.ie (We also will be releasing a completely new website shortly, so stay tuned!)
Lenovo appear to have screwed something up…..
If you have fingerprint software, or facial recognition software installed on your lenovo you are going to get the message "looking for credential tiles" stuck on your screen.
Uninstall that crap, and type your password in ;)
Hello readers! You probably already know, but from the Office SBS Blog, news that the Best Practices Analyzer has been updated.
OK people, as of right now, even though it states on the Sage website that Sage 50 2011 will work with with Outlook 2010, it does NOT!
This is quite unbelievable as a YEAR ago I contacted some people internally in Sage with the then Beta of Outlook 2010 to report that Outlook 2010 X64 edition did not work as was told that they would have this fixed by the next release.
Yet, here we are, again……
I have started a thread with the people in Sage, lets hope the development team get this sorted quickly!
More Posts « Previous page
- Next page »