Key resourcesTop issuesService Pack 1Install, upgrade and activatePerformance and maintenanceSecurity and updatesPrinting and hardwareFiles, folders, backup and recoveryDesktop and personalizationEmail, networking and onlineSound and videoSupport options
15 January, 2012
Support for Windows 7
Labels:
support,
Support for Windows 7,
windows 7
Location:
Mumbai, Maharashtra, India
Windows 7 and Windows Server 2008 R2 Service Pack 1
Windows 7 and Windows Server 2008 R2 SP1 helps keep your PCs and servers on the latest support level.
Here is the link from which we can download the service pack 1 for windows 7 and windows server 2008 R2: Service Pack 1 download
Some useful links:
Learn how to install Windows 7 Service Pack 1 (SP1)
Windows 7 Service Pack 1 RTM Build 7601.17514.101119-1850
Windows 7 Service Pack 1 is Ready for Download
Download Windows 7 SP1
Microsoft Windows 7 Service Pack 1
Here is the link from which we can download the service pack 1 for windows 7 and windows server 2008 R2: Service Pack 1 download
Some useful links:
Learn how to install Windows 7 Service Pack 1 (SP1)
Windows 7 Service Pack 1 RTM Build 7601.17514.101119-1850
Windows 7 Service Pack 1 is Ready for Download
Download Windows 7 SP1
Microsoft Windows 7 Service Pack 1
Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted.
Health check error after applying August 2011 CU for SP2010
Microsoft has published a very good article on this:http://support.microsoft.com/kb/2622705
As per the above article, it states that: Cause: This error is thrown due to a flaw in the logic of the owning health rule.
Resolution: Microsoft acknowledges that there is a flaw in the health rule logic and will resolve this issue in an upcoming CU. In the meantime, this error can be ignored.
Microsoft has published a very good article on this:http://support.microsoft.com/kb/2622705
As per the above article, it states that: Cause: This error is thrown due to a flaw in the logic of the owning health rule.
Resolution: Microsoft acknowledges that there is a flaw in the health rule logic and will resolve this issue in an upcoming CU. In the meantime, this error can be ignored.
Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted (SharePoint Server 2010)
Rule Name: Verify that the critical User Profile Application and User Profile Proxy Application timer jobs are available and have not been mistakenly deleted.
Summary: User Profile Service Application or User Profile service proxy timer jobs are not available and might have been deleted.
Cause: A required timer job for the User Profile service or the User Profile service proxy is missing.
Resolution: Edit the rule definition so that the configuration is automatically repaired.
1. On the Central Administration Web site, click Monitoring.
2. On the Monitoring page, in the Health Analyzer section, click Review rule definitions.
3. On the Health Analyzer Rule Definitions – All Rules page, in the Category: Configuration section, click the name of the rule.
4. In the Health Analyzer Rule Definitions dialog box, click Edit Item.
5. Select the Repair Automatically check box, and then click Save.
The system automatically creates the missing timer jobs.
If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happyJ to help you as well as resolves your issuesJ
SP2010: "Open with Windows Explorer" option is displayed in the "Actions" menu of Document libraries after disabling Publising feature
Problem description: Open with Windows Explorer option is displayed in the "Actions" menu of Document libraries after disabling Publishing feature
One of our user using a SP2010 team site from a long time. As per the requirements arises, he made some changes in the contribute permissions and activated “publishing feature” also.
What exactly happens?
After changing contribute permission of users to exclude “Use Client Integration Features" option, enabling Publishing feature results “Open with Windows Explorer” action to be available in the “Actions” menu of Document libraries. Later if we disable Publishing feature, that does not prevent users to open Windows explorer through “Open with Windows Explorer” option.
Troubleshooting started:
Let’s do the postmortem of this publishing feature.
Publishing feature is well known feature but it makes drastic changes when we do the activation.
Base location of publishing feature-C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\PublishingSite
Feature Id: F6924D36-2FA8-4f0b-B16D-06B7250180FA
Which features gets activated when we activate SharePoint Server Publishing Infrastructure at the site collection level:
Name:Publishing Prerequisites
Description: Enable Publishing prerequisites for site collection
Folder name: PublishingPrerequisites
Feature Id: A392DA98-270B-4e85-9769-04C0FDE267AA
Functionality:
This feature enables the publishing prerequisites for a site collection. It doesn’t activate any other features; it just runs the code in the feature receiver to set up a site so it can use the publishing features.
Name:Publishing Resources
Description: Enable Publishing for site collection
Folder name: PublishingResources
Feature Id: AEBC918D-B20F-4a11-A1DB-9ED84D79C87E
Functionality:
This feature enables the publishing resources on a site collection. The publishing resources are site columns and content types and site settings. The feature also contains three feature upgrades that are added to the feature when it gets activated.
Groups created when we activates Publishing feature:
Style Resource readers
Designers
Approvers
Restricted Readers
Quick Deploy users
Hierarchy managers
Cause:
Even after disabling Publishing feature, the groups that are created as part of enabling publishing feature are NOT removed. When enabling publishing feature, by default all users are added to a SharePoint group called “Style Resource Reader” . This group has "Read" permission by default which also includes “Use Client Integration Features" permission level by default. Because of that reason, users will get “Open with Windows Explorer” action in the “Actions” menu of Document libraries.
Workaround/Fix that found:
We only have workarounds for this behavior.
Workaround 1:
Remove “Style Resource Reader” SharePoint group.
Workaround 2:
Create a new SharePoint Group that does not include "Limited Access" permission level for it. Then add required users to that SharePoint group.
If you have any queries/questions regarding the above mentioned information then please let me know.
I would be more than happyJ to help you as well as resolves your issuesJ
Location:
Mumbai, Maharashtra, India
Subscribe to:
Posts (Atom)