Dated 13 dec
Its looks a bit scary but its in there. http://bit.ly/hanGqB
s60000cc1_4_0.exe 13-Dec-2010 07:52 5.4M
Thanks to Andre Blumberg for finding this out in the den...
Ok so it turns out that the Account (Usually RTCReportPack) you set up when you publish the Reporting Services reports needs to have the ‘Allow Log on Locally’ user right on the SQL server.
If not you will see this error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source ‘CDRDB. (rsErrorImpersonatingUser)
Logon failed. (rsLogonFailed)
For more information about this error navigate to the report server on the local server machine, or enable remote errors.
And make sure that it has Password never expires as well if that is ok with your service account security policy that is.
Im changing a Lync standard server from one hw to another and while moving the Central Management Server I tried to just run “ Install-CsDatabase –CentralManagementDatabase “
That resulted in
Error: Error connecting to “server.fqdn.local” while installing “CentralMgmtStore”. Verify that the SQL instance is running, connections are not being blocked by a firewall, and that you have SQL administrator permissions. For details, see the following log file: “C:\Users\user\AppData\Local\Temp\Create-CentralMgmtStore-server.fqdn.local-[2010_12_28][13_24_51].log” 2010-12-28 13:25:57 Error
└ Error: An error occurred: “Microsoft.Rtc.Common.Data.SqlConnectionException” “A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)” 2010-12-28 13:26:13 Error
Well it was an easy fix.
Make sure to run the full command and –clean
Install-CsDatabase -CentralManagementDatabase -clean -sqlserverfqdn server.fqdn.local sqlinstance rtc
Some other things to keep in mind
All credits for the below list should go to Randy Wintle
Before you move the Central Management Server, you must do the following:
1. Verify that you have created the new Central Management store. This is d
one by running the Install-CsDatabase cmdlet and using the CentralManagemen
2. If you are moving the Central Management Server to a Standard Edition se
rver, verify that you have used local setup to run the Prepare Standard Edi
tion server option. This advance preparation is required to add firewall ru
les that will allow Windows PowerShell to remotely access the new Central M
3. Verify that there is enough free disk space on the computer where Move-C
sManagementStore is being run to accommodate the Central Management Server.
4. Verify that the Front End Server service has been installed on the compu
ter where Move-CsManagementStore is being run. If this service is not insta
lled, and running, then the move will fail.
5. Verify that you can successfully run the Enable-CsTopology cmdlet on the
computer where Move-CsManagementStore is going to be run. If Enable-CsTopo
logy cannot be run on that computer then the move will fail and you will no
longer have a functioning Central Management store.
After you have completed these steps, all you need to do to move the Centra
l Management Server from Pool A to Pool B is log on to a computer in Pool B
and then call Move-CsManagementServer without any additional parameters:
When you do that, Move-CsManagementServer will consult the topology to dete
rmine the prior location of the Central Management Server (Pool A), and th
en transfer the Central Management Server and the Central Management store
to the current pool (Pool B).
If the move succeeds, Move-CsManagementServer will display a list of comput
ers on the screen. In order to finish the move, you must run local setup on
each of these computers. Computers in Pool A will still be running an inac
tive version of the Central Management service; running local setup will de
lete that service. The computer in Pool B where the Central Management Serv
er was moved will be running the Central Management service; however, other
computers in the pool will not. Running local setup on these computers wil
l install the Central Management service.
Event ID: 5021
Source: Windows Process Activation Service (WAS)
The identity of application pool LSGroupExpAppPool is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request. If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.
The issue was caused by a Group Policy that was conflicting with the rights applied by the OCS installation to the ‘Log on as a batch job’ and ‘Log on as a service’ user rights in the Local Security Policy on the OCS server.
The fix is to ensure that the RTC Service and RTCComponentService accounts have the ‘Log on as a batch job’ and ‘Log on as a service’ user rights on the OCS server. This right can be found in Local Security Policy > Computer Configuration > Windows Settings > Local Policies > User Rights Assignment. Either remove the conflicting Group Policy and fix the Local Policy or add the rights to the Group Policy.
There are currently only three downloads on the topic Office365 on download.microsoft.com
But if you are in to Office365 they are worth reading.
These documents provide a detailed description of the features and functionality of Office 365 services currently in beta.
FOPE Office 365 Beta documentation, including explanations of new FOPE connector features available to Office 365 Beta participants.
These documents provide an overview of the features and benefits of the Office 365 services currently in beta.
Ok so I’m living my 3 screens and a cloud life and all is great, I stream / download all the music I want and haven’t been a pirate for many years now. Until I wanted to look at a music video in my WP7.
So a 3 minutes SD music video is 159 points that’s 3 min of standard def for 159 points folks…
I mean come on, I can just go to Youtube and look at the same video for FREE in HD
and the best part of this is that a fairly new blockbuster movie is only 320 point?
So there is something seriously messed up with the music industry and how they do their pricing of music videos for zune compared to youtube.
There are two new end user portals online for Microsoft partners and customers playing around with the Office 365 beta