Hide the Site Actions button in SharePoint 2007

You guys ever get those crazy requests too from your boss? Things that really don’t matter at all and they only want to do it, because they thought of the idea. Well I get those all the time. This time it was to hide the Site Actions for our new SharePoint 2007 setup. I mean really, who cares if users can see the link/button, they can’t do anything and they’re used to seeing it from SP 2003 so it’s not like they’ll get confused about it. But anyway, the good team player I am I went in and figured out how to do it for us.

I’m not sure if this will work for everyone. I also did this like 6 months ago after searching for a few hours and not really finding anything. Probably because no one else care. But anyway, You should just have to wrap/replace your Site Actions code in your Template and it should hide the button from those who don’t have access to use it. I hope this helps out some of you out there that have the same request.

 

  Code:

<style type="text/css"> 

#LeftNavigationAreaCell {  

    display:none; 

} 

</style> 

<SharePoint:SPSecurityTrimmedControl PermissionsString="AddAndCustomizePages, ManageLists" runat="server"> 

                <style type="text/css"> 

                               #LeftNavigationAreaCell { 

                                display:block; 

                } 

                </style> 

                <table height=100% class="ms-siteaction" cellpadding=0 cellspacing=0> 

                 <tr> 

                       <td class="ms-siteactionsmenu" id="siteactiontd"> 

                       <SharePoint:SiteActions runat="server" id="SiteActionsMenuMain" 

                        PrefixHtml="<div><div>" 

                        SuffixHtml="</div></div>" 

                        MenuNotVisibleHtml="&amp;nbsp;"><CustomTemplate> 

                        <SharePoint:FeatureMenuTemplate runat="server" FeatureScope="Site" Location="Microsoft.SharePoint.StandardMenu" GroupId="SiteActions" UseShortId="true"> 

                            <SharePoint:MenuItemTemplate runat="server" id="MenuItem_Create" Text="<%$Resources:wss,viewlsts_pagetitle_create%>" Description="<%$Resources:wss,siteactions_createdescription%>" ImageUrl="/_layouts/images/Actionscreate.gif" MenuGroupId="100" Sequence="100" UseShortId="true" ClientOnClickNavigateUrl="~site/_layouts/create.aspx" PermissionsString="ManageLists, ManageSubwebs" PermissionMode="Any" /> 

                            <SharePoint:MenuItemTemplate runat="server" id="MenuItem_EditPage" Text="<%$Resources:wss,siteactions_editpage%>" Description="<%$Resources:wss,siteactions_editpagedescription%>" ImageUrl="/_layouts/images/ActionsEditPage.gif" MenuGroupId="100" Sequence="200" ClientOnClickNavigateUrl="javascript:MSOLayout_ChangeLayoutMode(false);" /> 

                            <SharePoint:MenuItemTemplate runat="server" id="MenuItem_Settings" Text="<%$Resources:wss,settings_pagetitle%>" Description="<%$Resources:wss,siteactions_sitesettingsdescription%>" ImageUrl="/_layouts/images/ActionsSettings.gif" MenuGroupId="100" Sequence="300" UseShortId="true" ClientOnClickNavigateUrl="~site/_layouts/settings.aspx" PermissionsString="EnumeratePermissions,ManageWeb,ManageSubwebs,AddAndCustomizePages,ApplyThemeAndBorder,ManageAlerts,ManageLists,ViewUsageData" PermissionMode="Any" /> 

                        </SharePoint:FeatureMenuTemplate> 

                        </CustomTemplate></SharePoint:SiteActions> 

                    </td> 

                 </tr> 

                </table> 

</SharePoint:SPSecurityTrimmedControl>

By: FreedomChicken

Read more »

How To Redirect To Exchange 2007 OWA in IIS 7 and Windows Server 2008

My company just setup our first Exchange 2007 cluster, and are getting ready to migrate our users over from Exchange 2003. Before we do that, we want to make sure everything is working correctly, and almost seamlessly to our users.

With that includes making the access to OWA (Outlook Web Access) in Exchange 2007 idiot proof. By default, there are two things that make idiot proofing difficult. For one, like most companies we set our OWA to require SSL. For two, the URL for OWA is https://servername/owa. No biggie right? Just tell the users to use that URL. Well, that won’t work too well for our users. We want to just tell them to go to “webmail” and have it work.

So here is what we did:

• In IIS 7, I clicked on the Default Website
• I clicked on Error Pages
• I clicked on 403, and selected Edit
• I clicked on the Respond with a 302 Redirect radio button, and inserted the URL to OWA:

• Done!

Now our users don’t have to type in HTTP or HTTPS, they can just open up a browser, type the server name/address in and automatically end up in the right place!

Has your company moved to Exchange 2007 yet? Have any problems with the migration? Did it go smoothly? How do you like Exchange 2007? Let me know in the comments!

Technorati Tags: exchange 2007,iis,owa,redirect,windows server 2008

Read more »

Installing ASP.NET on Windows XP

One would think that if they have .NET installed on their computer and they install the IIS that would be all you have to do.


Well as with many things that should be that easy it's not. But it is easy to fix.

1. Click Start then Run.
2. Type CMD and hit Ok.
3. Navigate to your Microsoft .NET windows directory which is usually C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
4. Run the following commands aspnet_regiis -i and aspnet_regiis -c
5. Load up your IIS Manager and enable ASP.NET on the site you want.

By: Sundance of Free TV Shows Online

Read more »

Removing Windows Components in Windows Vista

I got a call out of the blue from a Navy buddy of mine who is stationed in Germany yesterday asking me how he can uninstall Windows Media Player from his new Windows Vista machine. Seeing as how I haven't gone down the Vista road yet I wasn't sure.

I thought it would be just like in Windows XP where you go into Add/ Remove Programs, then go into Add/Remove Windows Components. Of course it wasn't that easy in Vista. No, once again they made a change for the sake of change.

In order to Add/Remove Windows Components in Windows Vista, you have to do the following:

1. Open Control Panel
2. In the left hand pane choose “Classic View”
3. Double click “Programs and Features”
4. Look in the left hand pane and click on “Turn Windows Features on or off”
5. Once the box is “updated” you will be able to Add/Remove Windows Components

I remoted into his computer in Germany using ShowMyPc and was able to go in and uninstall it for him. I'm glad to know that even though I am no longer in the Navy, I can still serve my country by helping a sailor out with his PC. By the way, this is also good to know if you want to add components too like IIS.

Do you know of an easier way to get to this in Vista? Let me know in the comments.

Read more »

Securing Unsecure Protocols

Do you have an FTP server running? Maybe you still use telnet for something on your network. Perhaps, you are a VNC user. Maybe you host your own web server, or POP3 e-mail server. All of the protocols used to make the services on those server work, are unsecured, and can easily be intercepted and/or monitored by third parties.

I already told you about Filezilla in a previous post, which uses FTPS, a secure file transfer protocol, but what if you are a fan of Microsoft's IIS service for running your FTP, or another unsecured FTP server software that still uses ports 20 and 21 and sends your passwords in plain text. Some people just don't like switching their server software. Sometimes due to laziness, and other times because it is too much of a pain.

There is a solution my friends, and it comes in the form of Open Source. It is called STUNNEL. STUNNEL provides a secure wrapper for any unsecured protocol you have, and encrypts the data connection using SSL. Take for instance my web server. Behind my firewall it is listening on port 80. My firewall, however is only open to port 443 (The port https uses). When you type https://pdbauer.com in your browser your traffic on port 443 gets forwarded through my firewall to my web server where STUNNEL is listening for 443 traffic. STUNNEL then forwards that traffic to port 80 where my web server service is listening. The whole process is encrypted using a self signed SSL Certificate I made using OpenSSL. Of course, you can do the same with a purchased certificate from a certificate authority like Comodo, Verisign, Thawte etc.

You can do the same thing to secure your POP3 e-mail, VNC, and FTP servers. There are so many options available with this, it really is a great tool for the security conscientious.

Read more »