Unable to remove Signature from a digitally signed Excel 2007 spreadsheet

Problem

You’ve made an attempt to sign an Excel 2007 spreadsheet with a certificate but noticed that you receive the following warning note when you reopen the spreadsheet:

Signatures

This document contains invalid signatures.

You attempt to remove the signature clicking on the arrow pointing downwards then selecting Remove Signature:

… answer Yes to:

Are you sure you want to permanently remove this signature? This action cannot be undone.

… only to receive the following message:

Signatures cannot be added or removed because this read-only workbook has been changed. To add or remove signatures, enable editing, save your changes, and then try again.

You’ve verified that enabling macros does not change this behavior:

Solution

I usually don’t blog about Microsoft Office applications because I’m not at all savvy with Excel or the other applications in the suite but as I had to assist with signing various Excel documents today for a client and ran into this problem and only finding 3 posts via Google with no resolution, I thought it would be a good idea to blog the resolution.

After spending half an hour or so going through the Excel help files and navigating around the menus to find a button that switched to editing mode, the way I finally got around this error message to remove the signed certificate was to open the spreadsheet, click on the top left corner button then select Save As –> Excel Workbook:

Save the file with a new file name:

Continue selecting Yes to the following message:

Saving a copy of this workbook will invalidate all of the signatures in the copy. Do you want to continue?

With the new file created:

… proceed with opening the file:

Click on the View Signatures… button:

Click on the arrow pointing downwards under the Invalid signatures window and select Remove Signature:

… answer Yes to:

Are you sure you want to permanently remove this signature? This action cannot be undone.

… and because you saved the original Excel spreadsheet to a new file, the signature should now successfully remove:

The signature has been removed and the document has been saved.

You don’t need to save the document at this point so you can just close it.

As easy as the process seems, it took me a bit of time to figure this out.  Hope this helps anyone out there who may come across this

Recomposing virtual desktops in a VMware View 5.x pool throws the error: “Internal View Composer error. Contact your administrator.”

Problem

You attempt to recompose virtual desktops in a VMware View 5.x pool from within VMware View Administrator but receive the following error message:

Internal View Composer error. Contact your administrator.

You’ve verified that the VMware View Composer service is started:

Solution

Before I begin, note that the error:

Internal View Composer error. Contact your administrator.

… is a very generic one and the best way to troubleshoot the issue is to navigate to the following directory where the VMware View Composer logs are:

C:\ProgramData\VMware\View Composer\Logs

… then open the vmware-viewcomposer.log file:

What I usually do is simply hit CTRL+F to bring up the Find window and search for the string error:

Traversing through the error entries revealed the following:

2012-11-27 00:38:59,840 | 3             | FATAL | Sim.ServiceCore.SimServiceApiImpl - Error: fail to execute web service call: AddDeploymentGroup
VMware.Sim.CommonLib.Exception.SimAdConnectionException: The specified domain does not exist or cannot be contacted. ---> System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException: The specified domain does not exist or cannot be contacted.
   at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)

The immediate idea I had after seeing how it appears to be an issue with the View Composer contacting the domain, is that we recently decommissioned old domain controllers so the DNS entries on the vCenter server where the View Composer resided was out of date.  Note the following entries in the DNS server addresses for the vCenter server’s NIC card:

The error went away once I updated the 192.168.1.x entries that point to the old DNS servers to the new ones.

**Note that if you’re wondering why we didn’t catch this earlier, it’s because the vCenter server in this environment is not joined to the domain.

Deploying Lync Server 2013 Persistent Chat Server

One of the semi new features I’ve been interested in since Lync Server 2013 was initially announced was the new Persistent Chat Server that replaces the Group Chat server.  Those who have worked with the older version of Group Chat would know that the feature doesn’t really feel like it’s tightly integrated with Lync and administration can sometimes feel a bit clumsy at times.  With that being said, I’ve seen several clients who have had success with the feature in their environment so I’m anxious to test it out now that Lync Server 2013 has RTM-ed.  This blog post will serve to demonstrate the deployment process and what the new Persistent Chat looks like.

SQL and File Store Requirements

Similar to the Lync Server 2010 front-end server, a SQL backend database and file share is required for the Persistent Chat Server.  The backend database is used to store chat history, configuration, user provisioning data and if the compliance option is selected, a Persistent Chat compliance database to store compliance data:

Technical Requirements for Persistent Chat Server
http://technet.microsoft.com/en-us/library/gg398495.aspx

Microsoft recommends to install a dedicated backend database server for the Persistent Chat Server but for smaller deployments, it is supported to have the database collocated on the same SQL backend database as the front-end server.  For the purpose of this example, we’ll be using the same backend database as the front-end server.

In addition to the backend database, a file share is also needed for a repository to store uploaded files so prior to the deployment of the server, create a file share on the preferred file server of your choice and share out the folder.

Define New Persistent Chat Server in Topology Builder

Prior to installing the new Persistent Chat Server we’ll need to define the new server in the topology so begin by launching Topology Builder and downloading the existing topology:

Define file store share:

Continue by right clicking on the File stores node to define a new store for the Persistent Chat Server:

Define New Persistent Chat Pool:

With the file store defined, proceed with creating the new Persistent Chat Pool:

We won’t be enabling compliance in this demonstration so leave the checkbox unchecked:

Since we’ll be using the same backend database as the front-end server, select that instance for the SQL Server store:

Continue by selecting the file store previously defined for the Persistent Chat Server:

Select the appropriate Lync Server 2013 pool for the next hop:

With the new Persistent Chat Server pool defined, proceed with publishing the topology:

Note that the Persistent Chat Server backend databases will automatically created and if you choose to let the wizard automatically determine where to put the database, ensure that the drives have more than 12GB of space or the creation of databases will fail (I increased the C drive by 5GB to a total of 17GB):

Once the topology successfully publishes, you should see the following 2 folders created in the file store:

• 1-PersistentChatService-9
• 1-PersistentChatService-10

You should also see a new database named mgc created on the backend SQL server:

Install Prerequisites

While the documentation for deploying the Persistent Chat server:

Deploying Persistent Chat Server
http://technet.microsoft.com/en-us/library/jj205357.aspx

… does provide quite a bit of information, it isn’t exactly as detailed as the front-end server role because all it says for prerequisites is the following:

The prerequisite software for Persistent Chat Server is the same as the prerequisite software for the Lync Server 2013 Front End Servers and the Lync Server 2013 Standard Edition server on which Persistent Chat Server features are installed.

The prerequisite software required for the Persistent Chat Server file store is the same as that for Lync Server 2013.

The prerequisite software for the SQL Server databases for Persistent Chat Server content and compliance is also the same as that for Lync Server 2013.

Assuming this means exactly what it reads then all we need to do is repeat the installation and configuration of the prerequisites we used for the front-end server:

Install Windows Roles and Features (including MSMQ):

Rather than manually going through Server Manager to install the roles and features, the following PowerShell cmdlets can be used to automatically install all of them.

Import-Module ServerManager

Add-WindowsFeature Web-Server, Web-Static-Content, Web-Default-Doc, Web-Scripting-Tools, Web-Windows-Auth, Web-Asp-Net, Web-Log-Libraries, Web-Http-Tracing, Web-Stat-Compression, Web-Default-Doc, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Errors, Web-Http-Logging, Web-Net-Ext, Web-Client-Auth, Web-Filtering, Web-Mgmt-Console, Web-Dyn-Compression, Web-Mgmt-Console, Desktop-Experience, msmq-server,msmq-directory

Restart the server once the executation of the cmdlet completes.

 

Install Microsoft .NET Framework 4.5:

Proceed with downloading and installing Microsoft .NET Framework 4.5 from the following URL:

http://www.microsoft.com/en-us/download/details.aspx?id=30653

Note that the link provided in the message prompt when you attempt to launch the Lync Server 2013 setup but don’t have Microsoft .NET Framework 4.5 installed is:

http://go.microsoft.com/fwlink/?LinkID=264944

Install PowerShell 3.0:

Continue and PowerShell 3.0 from the following URL: http://www.microsoft.com/en-us/download/details.aspx?id=34595

There’s a list for 4 items for download and the way to determine which one you’re supposed install is actually noted at the bottom. Since we’re installing PowerShell 3.0 onto a Windows Server 2008 R2 SP1 server, proceed by downloading the following file:

WINDOWS6.1-KB2506143-x64.MSU

Install Windows Identity Foundation:

Continue and Windows Identity Foundation from the following URL: http://www.microsoft.com/en-us/download/details.aspx?id=17331

Windows6.1-KB974405-x64.msu

Launch Setup:

Launching the Setup.exe executable for the Lync Server 2013 binaries will automatically install Microsoft Visual C++ 2012 x64 Minimum Runtime – 11.0.50727 Package so don’t bother downloading it:

Install the Microsoft Visual C++ 2012 x64 Minimum Runtime – 11.0.50727 Package:

The setup wizard will be presented to you once the Microsoft Visual C++ 2012 x64 Minimum Runtime – 11.0.50727 Package is installed:

Proceed by through through the installation wizard:

Deploying the Persistent Chat Server

Install Local Configuration Store:

With the Central Management Store populated with the new topology, proceed by launching the Lync Server 2013 – Deployment Wizard on the front end server, click on the Install or Update Lync Server System link:

… then the Run button for Install Local Configuration Store:

Setup Lync Server Components:

Once the local configuration store has been installed, proceed with installing the Lync Server Components:

Request, Install and Assign Certificates:

Once the Lync Server components have been installed, proceed with requesting, installing and assigning certificate for the server:

**Note that you can either create the certificate as exportable or not. I prefer to have an exportable certificate so I could back it up.

Start Services:

With the certificates issued and assigned, proceed with starting the services:

Check Service Status:

Every though the last step Service Status is listed as option, it’s always best to perform it anyways to ensure that all the services are listed as Started:

• Lync Server Centralized Logging Service Agent
• Lync Server Persistent Chat
• Lync Server Replica Replicator Agent

Adding a Persistent Chat Administrator

The deployment of the Persistent Chat Server should automatically create CsPersistentChatAdministrator group that is used to grant administrators permissions to administer the Persistent Chat Server. Proceed by adding the user account or accounts that will be used for administration:

Configuring Persistent Chat Server

With the appropriate permissions granted to users who will be administering the Persistent Chat Server, proceed by launching the Lync Server 2013 Control Panel to configure the following:

• Configure the Global Policy for Persistent Chat
• Create a Site Policy for Persistent Chat
• Create a User Policy for Persistent Chat
• Apply a Persistent Chat Policy to a User or User Group

I won’t actually be creating policies for sites or users but rather just simply enable it in the default Global policy as shown in the following:

For more information on how to configure policies for more granular control, see the following:

Enable Persistent Chat Server Policy
http://technet.microsoft.com/en-us/library/jj205056.aspx

Persistent Chat Configuration:

Several configuration parameters are available for each Persistent Chat policy created.  We won’t be changing the defaults of the global policy we’ll be using but the following are the settings available:

Configure a Category for Persistent Chat:

Before we can create rooms, we need to configure categories so proceed to click on the Category node in the Lync Server 2013 Control Panel:

From within the Category window, click on the New button to create a new Category:

Continue by selecting the service and then click the OK button:

In the New Category window, type in a name for the Name field and check the following:

• Enable invitations
• Enable file upload
• Enable chat history

In the Allowed members section, add users who you want to be members of the category:

Scrolling down the window will reveal sections to add denied members and creators:

Proceed with adding the members you want grant permissions for creating rooms and then click on the Commit button to apply:

From within the Lync Client of the members that were added to the category, we should see an additional icon:

**Note: Try logging off and on the Lync client if the Chat Room icon isn’t shown.

Clicking on the Chat Room icon will bring up the following window that usually lists rooms the user is in but since we don’t have any rooms configured, we’ll proceed to click on the + icon to create one:

Clicking on the + icon and the Create a Chat Room… button will launch the browser to the following page:

Continue by clicking on the Create A New Room button:

Fill in the required fields, add the members you would like to be a part of the chat room and then click on the Create Room button to create the room:

With the room created, you should now notice a notification in the Lync Clients of the users who were added as members indicating that they jave a new chat room invite:

Double clicking on the new list item will bring up the window for the chat room:

Creating Chat Rooms with PowerShell:

If administrators want to maintain more control on what rooms can be created thus not granting users the ability to create rooms, PowerShell can be used instead to create rooms.  The full list of available cmdlets are available in the following URL:

Configuring Persistent Chat Server by Using Windows PowerShell Cmdlets
http://technet.microsoft.com/en-us/library/jj204877.aspx

The following is an example of a cmdlet that will create a new chat room named PowerShell Talk

New-CsPersistentChatRoom -Name “PowerShell Talk” -PersistentChatPoolFqdn svr-lyncpc-01.ccs.int -Category “Test Category”

With the room created, we can add users with the following cmdlet:

Set-CsPersistentChatRoom -Identity “PowerShell Talk” -Members @{Add="sip:tluk@ccs.bm", “sip:LyncTest@ccs.bm”}

The user you added as a member to the room should now see a new chat room available:

To remove the room that was just created PowerShell, use the following cmdlet:

Remove-CsPersistentChatRoom -Identity “PowerShell Talk”