Custom presence in Lync 2010

I enjoyed using custom presence in Communicator 2007, but when our enterprise switched to Lync 2010 a few months ago, my custom presence migrated through until I switched to a new PC, then the old method of enabling custom presence failed.  Why?  One registry entry…

Here’s how to do it: Create a string key in HKCUSoftwarePoliciesMicrosoftCommunicator called CustomStateURL and give it a value of the path to an OCS presence XML file, such as file:///c:/program files/Microsoft Office Communicator/OCSPresence.xml

Now, also create a DWORD key in the same location called EnableSIPHighSecurityMode and give it a value of 0.  This entry wasn’t needed in Communicator 2007, and is something an administrator can turn off in Lync, but can be handled individually at your PC also.

Finally, make sure the OCS presence XML file is in the path you specified above and log off/on.  You should be good to go!

The link to the ZIP file that has both the .reg file and .xml file is here.  Enjoy!

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube

SharePoint 2010 Workflow Status filtering

Since MOSS 2007, SharePoint workflow statuses display with a text value such as “Canceled”, “Completed” or “In Progress”, but behind the scenes are stored as a key with an integer value.  So in a view when you want to filter based on the workflow status you must use this key value, and not the display text.

As an example, here’s what the Filtering section would look like if I were filtering out items where the workflow status were either “Completed” or “Canceled”:

Here are the values and definitions for each workflow status, which still apply in SharePoint 2010:

  • 0 – Not Started
  • 1 – Failed On Start
  • 2 – In Progress
  • 3 – Error Occurred
  • 4 – Canceled
  • 5 – Completed
  • 6 – Failed On Start (retrying)
  • 7 – Error Occurred (retrying)
  • 15 – Canceled (defined but not used)
  • 16 – Approved
  • 17 – Rejected

Hope this serves as a quick reference, it will for me!

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube

Customizing the Request Access page in SharePoint 2010

Our organization, like many others, handles access requests for all applications through our IT Support desk. Additionally, documentation is required and must be approved by the user’s department manager before the access can be granted. After just recently migrating the entire company’s intranet over to SharePoint 2010, I wanted to allow users to request access, so I made sure the Manage Access Requests was selected by default for all resources. However, within a week of moving it over I’m getting requests for all sorts of things in my inbox every day, even from our kiosk service accounts in the employee break room or at terminals, which are both locked down intentionally. I don’t mind the access requests, but there needs to be a consistent way of handling requests that complies with our internal standards.

I did some research into the Access Request email message that comes from SharePoint, thinking maybe I can modify the timer job, workflow, email content, etc. Nothing. In fact, the very same discussion is held in a TechNet article located here. Bummer, this would have been ideal.

So what’s the next best step? Modify the reqacc.aspx file in C:\program files\common files\microsoft shared\web server extensions\14\template\layouts.

Here’s what the original page looks like:

** WARNING: Make a copy of the original file BEFORE modifying! Making changes to the layouts folder in SharePoint is always at your own risk! If for any reason your changes are unsuccessful, you can always delete that file and place the copied original back in the folder to restore functionality!

That being said, here’s what I did to create a custom Request Access page:

1. Navigate to your layouts folder, typically located at c:\program files\common files\microsoft shared\web server extensions\14\template\layouts
2. Make a copy of the reqacc.aspx file and put it somewhere safe. Make NO changes to this copied file!
3. Open the other reqacc.aspx file (not the copy) in your editor of choice.
4. Near the bottom, locate the following section of code:


This is the section of the page that says “Type your request, and then click Send Request.” Deleting it breaks the page because SharePoint is looking for specific elements in the page, so all I did was hide it by adding the following CSS attribute:


This will override the CSS class settings and hide the element altogether. Do the same thing to the textarea below it, to prevent users from entering in anything:




This is the textbox that says “Supply a description of the action you were taking and the URL you were trying to reach.” I hid the entire element by adding the same style attribute like so:



5. If you want to enter a custom message or instructions for the user to follow, I put that in place of the input button in the next table row below the textarea, located here:




Here is a sample of what I replaced it with:


To request access, please fill out a User Access Request Form locatedhere.  Make sure the resource you need access to is listed in the form, including the URL listed above.

Save the file and the changes are immediate. The end result will look something like this:

You could theoretically change this page however you want, but I liked the existing simplistic layout, it got to the point and provided the end user with enough information. Of course, custom application pages can be made and used in SharePoint nearly anywhere.  Hope this helps!

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube

Remove “Recently Modified” from Quick Launch in SharePoint 2010

While messing around with SharePoint 2010 pages today, I remembered I wanted to find a way to remove the “Recently Modified” section from the Quick Launch area.  This was a very easy fix, as explained by John Dandison.

Add a Content Editor Web Part to any section of the page and put this in the HTML:


Now THAT was easy!  Sure you can also do this in SPD, but for me this was a LOT easier for a page here and there.  If I wanted to create a page template going forward, just modify the master page for this item in SPD by adding the DISPLAY:none; to the .s4-recentchanges CSS element!

Eric

Eric Oszakiewski is a professional software developer based in Scottsdale, AZ with over 35 years of IT experience, and 19 years Native American Gaming experience. He is currently working as a Sr .Net/SharePoint Developer for General Motors, and also as a consultant.

More Posts - Website

Follow Me:
TwitterFacebookLinkedInGoogle PlusYouTube