By BoonTee,on February 22nd,2012% Whenever Sharepoint is updated,psconfig must be run to finish the installation of the update. See the SBS Blog here –http://blogs.technet.com/b/sbs/archive/2011/05/24/you-must-manually-run-psconfig-after-installing-sharepoint-2010-patches.aspx To run pscoonfig,perform the following: - Open up a Command Prompt as Administrator
- Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
- Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Other possible issues after installing Sharepoint Foundation 2010 SP1,or other updates can be found here –http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx By BoonTee,on February 21st,2012% This is becoming a more common problem on Windows XP PCs. It appears to have been corrupted by a faulty update. To fix the issue,press CTRL-ALT-DEL at the blank screen and start the task manager. From the Task Manager,select File,New Task (Run). In the Task windows,type CMD,then press the OK button. The error message will appear a few more times,but the Command Prompt will eventually appear. From the command prompt,type CD C:\WINDOWS\SYSTEM32\DLLCACHE Then type COPY IERTUTIL.DLL .. This will copy the correct version of iertutil.dll to the C:\Windows\System32 folder. If the file is not found,you can type in DIR C:\WINDOWS\IERTUTIL.DLL /S/E A list of files and locations will show up. You can copy the files from any of those folders. After this,reboot the system and the problem showld be fixed. By BoonTee,on January 17th,2012% The SBS Teem have released a Powershell commandlet that will allow you to fine tune and manage the reporting and alerting functions in SBS 2008 and 2011. There are a number of alerts that can be safely ignored and yet persist in the event alert reports,which often cause anxiety and uneccesary concern. This commandlet will allow you to configure and specify which alerts to ignore,thus providing less noise to work through in order to see the important alerts more clearly. The blog provides more information here –http://blogs.technet.com/b/sbs/archive/2012/01/16/managing-event-alerts-in-your-reports-an-sbs-monitoring-feature-enhancement.aspx By BoonTee,on December 14th,2011% Chaning the password regularly is a good thing to do. However,this can be quite messy at times,especially when you have a number of devices that depend on this password. It is often easier to set a long and complex password,and to set it once. In this case,you may wish to disable the password expiration policy which is set by default to 90 days. To do this,you will need the Microsoft Online Services Module for Windows PowerShell. There is a 32bit and 64bit version. You can download them here –http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh124998.aspx#BKMK_install Once it has been installed,run the PS Command Shell and type the following commands (copy and paste). - PS>$cred = get-credential
- Type in the Office365 Admin user. This is usually in the form of admin@[companyname].onmicrosoft.com
- PS>Connect-MsolService –Credential $cred
- PS>$users = Get-MsolUser
- PS>foreach ($user in $users){Set-MsolUser –UserPrincipalName $user.UserPrincipalName –PasswordNeverExpires $true }
That’s it. This will disable the password expiration policy for all users for this organisation. To check this,type PS>get-msoluser | select displayname,passwordexpirationdate By BoonTee,on November 2nd,2011% Sometimes,a PC may have been disconnected from the network,and the password for the Client/Server Security Agent (CSA) for Trend Micro’s Worry Free Business Security is unknown or lost or forgotten. The following knowledge base article describes how to uninstall the agent if this case arises –http://esupport.trendmicro.com/solution/en-us/1036275.aspx Basically,it involves setting the registry key “Allow Uninstall”to 1.
For WFBS versions 5.x and 6.x,this key is located here –HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc
For WFBS versions 7.x,this key can be found here –HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\UniClient\1600\Misc By BoonTee,on September 14th,2011% In migrations of Virtual Machines,this scenario may happen. You may have created a VHD using a P2V utility,and go to boot the VM. The VM fails to start,often with the message above. Microsoft have release a KB article on this here –http://support.microsoft.com/default.aspx?scid=kb;en-US;2249906 This is caused by incorrect permissions on the VHD. The resolution is as follows: - Note the Virtual Machine SID
- Using icacls in an elevated prompt,type icacls [VHD file] /grant “NT VIRTUAL MACHINE\[VM SID]“:F
By BoonTee,on July 13th,2011% A repair guide for SBS 2011 Standard has been released here –http://technet.microsoft.com/en-us/library/gg697169.aspx The topics covered include: - Manage Windows Small Business Server 2011 Standard applications
- Repair administrator account access to SharePoint Foundation 2010
- Repair client deployment issues
- Repair email anti-spam software
- Repair email programs and Microsoft Exchange Server services
- Repair folder redirection and shared folders
- Repair Microsoft Exchange Server roles in Windows Small Business Server 2011 Standard
- Repair Monitoring and Reporting Features in Windows Small Business Server 2011 Standard
- Repair Remote Web Access
- Repair Remote Desktop Gateway
- Repair the Move Exchange Server Data task
- Repair the POP3 connector
- Repair the Windows Small Business Server 2011 Standard Console
- Repair Users and Groups features
- Repair Windows Server Backup
- Repair Windows Server Update Services
- Repair SharePoint Foundation 2010
- Repair SharePoint Foundation 2010 after moving the databases
- How to synchronize the DSRM password with the Windows Small Business Server 2011 Standard network administrator password
- How to manually create required Group Policy objects for Windows Small Business Server 2011 Standard
- How to remove the SSL binding to an incorrectly published certificate
By BoonTee,on June 1st,2011% This scenario has been coming up fairly often recently. A PC becomes infected by a Fake-AV software. MalwareBytes (www.malwarebytes.org) cleans up the infection. Suddenly,EXE files cannot run. Not even Regedit. There are a couple off good resources which help fix up the registry and restore the EXE file association back to normal. Download and unzip the reg files. Right Click on the Reg file and select Merge. Thanks and acknowledgements to Doug Knox and Ramesh Srinivasan. They have more file association fixes listed below. By BoonTee,on May 13th,2011% The error above happened to me today when setting up a new Virtual Machine on a brand new HyperV Server running on Windows Server 2008 R2 Exterprise. Microsoft Support have a Knowledge Base article on this here –http://support.microsoft.com/kb/2249906 Basically,the fix is to copy the Virtual Machine ID and run the icacls command from an elevated command prompt. eg. icacls “E:\VMs\VMName\Disk0.vhd”/grant “NT VIRTUAL MACHINE\5FC5C385-BD98-451F-B3F3-1E50E06EE663″:F By BoonTee,on April 14th,2011% After using the very early Pending.XML file edit fix as described in my earlier blog the Windows 7 PC would be left in a torn state. This meant that Service Pack 1 could no longer be installed on this PC,and possibly other patches as well. There are two options for recovering from this. First,you could reimage or rebuild this PC. This is often not a solution,especially if there were vaarious bits of information that could not be easily reinstalled. The other option is to repair the current system. Some people have had success in using a Windows 7 SP1 DVD or USB to do a repair install over the top of the current installation. If that does not work,Kelvin Aston provides a step by step set of instructions for repairing the system here –http://kelvinaston.blogspot.com/2011/04/possible-fix-for-torn-sp1-machines.html Note:I have not been able to find a PC in a torn state in order to test out this fix myself. | |
Recent Comments