How to broadcast message using OCS (Solved)

Broadcast your message in OCS

OCS supports command line application which will broadcasting messages to all users who were logged into OCS infrastructure . Sometimes administrator needs to warn users about upcoming outage or any incident throughout the organization and this is an easiest way of doing it. The user who needs to sends the broadcast should  be a member of RTCUniversalServerAdmins group and preferably the admin user should logged  into any of the FE server for better performance.

Step 1.

Login into any of the FE server and search for lcscmd.exe on it. It will be in the installation folder of Office communications software, or else you will get it in the installation CD of OCS server.

Step 2.

Open command prompt and change the directory where you have located lcscmd.exe

For me it is

C:\Users\administrator.UST\Desktop\OCS 2007 R2 X64 Ent Edition Server\2007R2\64BIT\Setup\amd64>  

Because I have a copy of the installation files in my desktop

Step 3.

Type the below command and hit enter

LCScmd /Server /Action:BroadcastMessage /Role:SE Message:"Type here your message"

/Role:SE indicates it is for Standard edition installation and replace with /Role:EE for enterprise users.

Note: in my EE installation I even run /Role:SE without any issue (so seems this change is optional)

Done !!!!!! :)

All users who logged in will get the message from noreply@yourdomain.com .

The output of the command clearly denotes whether the command run successfully,how many users received this message, how many failed and also a log file will also generate on the %temp% folder which will completely describe the command execution flow including the error logs

How to get communicator chat or conference logs

Get communicator chat logs from Achieving server

Previously OCS administrators were not confident enough to get Old chat logs because it requires more complex  SQL queries  to get chat logs exported from OCS Achieving server .Now MS released a new tool "OCSArchiveViewerSetup" which is having a GUI to retrieve the chat logs easily.

In the achieving and monitoring server install OCS Achieving tool "OCSArchiveViewerSetup". This is a free tool and the installation doesn’t cause any service interruption (as I experienced)  .It can be downloaded from microsoft (just google it )..After installation it will ask for database to locate .Add the server name and instance name (ServerName/Instance) if default installation no need to specify instance name, and click Connect.

Put the complete sip Uri of the user to get the chat log. There is an option to select the time limit to get more refined chat logs .The tool is having an option to export the chat logs to IE too.

PLEASE IGNORE - Temporary item created by Microsoft Conferencing Add-in for Outlook (Version 8.0.6362.187)

Error

I faced similar issue with Conferencing add-in Version 8.0.6362.143 and 8.0.6362 .187 versions .And users were receiving empty appointments in their calendar. With subject line

PLEASE IGNORE - Temporary item created by Microsoft Conferencing Add-in for Outlook (Version 8.0.6362.187)

Resolution

I updated the Conferencing add-in with Version 8.0.6362.190 (or above will help ) and resolved the issue

Rule "Reporting Services Catalog Temporary Database File Existence" failed.

Error :

Rule "Reporting Services Catalog Temporary Database File Existence" failed.

Solution

Open the folder
"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA"
Delete the below files from the folder

ReportServer.mdf
ReportServer_log.LDF
ReportServerTempDB.mdf
ReportServerTempDB_log.LDF

After deleting the above files ,click Re-run in the setup window

Rule "Reporting Services Catalog Database File Existence" failed

Error :
Rule "Reporting Services Catalog Database File Existence" failed

Solution

Open the folder
"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA"
Delete the below files from the folder

ReportServer.mdf
ReportServer_log.LDF
ReportServerTempDB.mdf
ReportServerTempDB_log.LDF

After deleting the above files ,click Re-run in the setup window

OCS installation :Windows Media Format Runtime is required in order to install this component

I was trying to install OCS 2007 R2 in Virtual environment

While installing Enterprise edition server I faced a popup as below

"The Windows Media Format Runtime is required in order to install this component. Installing the WMFR may require a system restart to complete the installation. Click OK to continue with the installation"

The issue is resolved after installing some desktop experience feature is installed as below

Open command prompt and type as below

Please make sure the shown *.mum is available in your path. If not find the similar one and change the name and run it

pkgmgr.exe /ip /m:"C:\Windows\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum"

Eg : C:\Windows\servicing\Packages\Microsoft-Windows-Media-Format-Package~*.mum and * may be any file which are available

Invoke or BeginInvoke cannot be called on a control until the window handle has been created (Solved)

Issue
I was trying to install SLL 2008 in a windows 2008 R2 64 Bit server and I faced an error while installation.

Error
SQL Server Setup has encountered the following error:

Invoke or BeginInvoke cannot be called on a control until the window handle has been created

Resolution (1)

After clicking the setup.exe I have closed all the explorer windows and tried to install and the issue didn’t happened again and I was able to install SQL

Resolution (2)

Restart the server first

Open the folder in which you have the SQL installer files.

Open the folder which suits your OS (X86 or X64) and find the file "LandingPage.exe"

Double click on it.

It will ask for the installer folder, select the parent installer folder and click OK.

Then the normal SQL installation pop up will come .

Close all windows other than this setup window (recommended), and do the installation

Cannot synchronize with corporate address book. This may be because the proxy server setting in your browser does not allow to access the address book. If problem persists please contact your administrator

Issue :Communicatior client couldnot showing addressbook entries

I faced an issue with a user saying that he is not able to browse corporate address book and showing an error

·         "Cannot synchronize with corporate address book. This may be because the proxy server setting in your browser does not allow to access the address book. If problem persists please contact your administrator."

Resolution

I have seen a lot of tutorials related to this but I found an effective way in resolving this issue

Open certificate store using mmc and select Computer certificates

Start-> run->mmc and hit enter

Click File -> Add /remove  snap-in and click add button in Stand alone tab

Select Certificate and click Add

Select Computer account and hit next

Confirm radio button at Local computer click finish and close

Hit ok and you will get certificate console

Open certificates under

1)Personal

2)Trusted root

3)intermediate certification authorities and remove all old certificates before todays date

Close the mmc

Open IE -> Tools-> internet options-> Advanced ->under security settings un-tick “Check for publisher’s certificate revocation

After that the issue is resolved

Join to Windows domain without connecting Domain server

Join to Windows domain without connecting Domain server

With Windows 7 and Windows Server 2008 R2, that process gets a bit shorter with the release of Microsoft's Offline Domain Join tool djoin.exe. This tool enables Windows 7 or Windows Server 2008 R2 computers to join a domain without needing to communicate with a domain controller (at least, at first). Exceptionally useful for massive desktop rollouts, this tool comes in particularly handy when automating the deployment of virtual desktops. Here's how you'll use it:

Step one requires the use of a domain-joined computer. This computer, which will be referred to as the provisioning computer, works with a domain controller to pre-populate information about the offline computer. From the provisioning computer, run the following command to create the necessary provisioning file:

djoin /provision /domain <domainName> /machine <offlineMachineName> /machineou <TargetOuToCreateAccount> /savefile <fileNameWithTxtExtension>

Running this command creates a text file that includes the necessary information for later adding this computer to the domain.

Step two involves copying the file you created in step one to the client computer, which has not been joined to the domain.

Step three completes the process by ingesting the information in the copied file into the offline client. This is done by running the following command on the offline client computer:

djoin /requestODJ /loadfile <fileNameWithTxtExtension> /windowspath %SystemRoot% /localos

Once complete here, reboot the computer to join it to the domain. You can further automate this process by adding a little scripting around the domain join steps, or even including its information in an unattend.xml file.