Category Archives : Uncategorized
How to migrate from Windows 8 Preview Releases- Default Installation
Windows 7 (English) with Service Pack 1
- Windows 7 Home Premium (x86) – 32 bit
- Windows 7 Home Premium (x64) – 64 bit
- Windows 7 Professional (x86) – 32 bit
- Windows 7 Professional (x64) – 64 bit
- Windows 7 Ultimate (x86)* – 32 bit
- Windows 7 Ultimate (x64)* – 64 bit
Using NTFS Junctions to Fix Application Compatibility Issues on 64-bit Editions of Windows
Sharepoint 2010 – Configuration Wizard error: The password supplied with the username domain\username was not correct. Verify that it was entered correctly and try again.
If you are running the SharePoint 2010 Products Configuration Wizard you may get the following error:
The password supplied with the username domain\username was not correct. Verify that it was entered correctly and try again.
This error occurs when you are reinstalling SharePoint on a computer where there had been a SharePoint installation earlier and the SharePoint Central Administration v4 website and application pool still exists in IIS.
To resolve the problem, open IIS and delete both the SharePoint Central Administration v4 website and application pool. Then the Configuration Wizard should run without problem.
The full error message from the logfile:
System.ComponentModel.Win32Exception: The password supplied with the username domain\username was not correct. Verify that it was entered correctly and try again.
at Microsoft.SharePoint.Administration.SPFarm.ValidateLogonAccount(String& username, SecureString password)
at Microsoft.SharePoint.Administration.SPManagedAccount.SetPassword(SecureString value)
at Microsoft.SharePoint.Administration.SPProcessIdentity.SetPassword(SecureString value)
at Microsoft.SharePoint.Administration.SPApplicationPool..ctor(String name, SPWebService service)
at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, SPProcessAccount processAccount, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures)
at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, IdentityType identityType, String applicationPoolUsername, SecureString applicationPoolPassword, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures)
at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance(SqlConnectionStringBuilder administrationContentDatabase, SPWebService adminService, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.CreateAdministrationWebService(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.CreateBasicServices(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
Reset the user password in Lion and Mountain Lion
Some of you ask for change the user password in 10.7 or 10.8, because the button was deleted.
With Mac OS X Snow Leopard and older Mac OS, the installer disc allows you to change the user password pressing Utilities > Password Reset. In Lion, it was deleted, but you can change it with easy steps. There are two ways to reset the user password in OS X Lion and Mountain Lion:
- In the system
If you boot in your system, you can change the password. It’s used to change it if you didn’t forget it.
- Boot your Mac and open System Preferences > Users and Groups
- You can see the users. Press the user what you want to change the password and select Change password. You will be asked for your password
- In Recovery
When you forgot the password and you can’t use OS X, you have to use the new Recovery.
- To boot in Recovery system, press Command and R keys in boot and hold the keys until you see the Apple icon. If you have a Mac with Internet Recovery, read > http://support.apple.com/kb/HT4718. If your Mac has got a wireless keyboard, hold them when you hear the startup sound
- When it starts, select Utilities > Terminal, and type:
resetpassword
Press your user and type your password. Finally, reboot.
This doesn’t work for FileVault. If you forget your password with FileVault, you lost your info. Also, you can see if you use Recovery HD or Internet Recovery, or enable it -> http://support.apple.com/kb/HT4904
You can do it with an USB drive > http://support.apple.com/kb/HT4848
IE prints blank page
http://www.mutterances.com/?p=83
Internet Explorer prints & previews blank pages (IE7, IE8, IE9)
When trying to print from Internet Explorer (or print preview), all you see is blank content, and some header and footer information. The footer reads something to the effect of:
“file:///C:/Users/userprofile/AppData/Local/Temp/Low/randomfile.htm”
This problem drove me nuts for some time. I first noticed it under Windows Vista with IE8, but from reading out there on the web, it potentially effects any windows system running IE7 onwards (so XP through to 7).
Specifically, I am rolling out Windows 7 at my firm, with IE9 bundled in as part of an Image file. In my case the problem was probably occuring after I installed IE9 using the admin account on the system that the master image was based on (we don’t want users to be able to install their own apps). If I log in to Windows with the admin account directly, all prints fine.
Anyway, enough rambling, you are here because you want to know how to fix it.
Firstly, the ‘Low’ folder mentioned above is needed as a temporary working folder for the HTML pages being generated and printed from IE. Start by bringing up a command prompt (run -> cmd), making sure you DO NOT run with elevated permissions (otherwise it will do this for your local admin account, which won’t help you). At the command prompt, run the following command:
mkdir %userprofile%\AppData\Local\Temp\Low
This will create the necessary Low folder in the right place, which is almost certainly absent otherwise.
Other posts I read suggested this was enough, but it isn’t. The newly created ‘Low’ folder won’t work until you run a further command which sets the integrity level of this folder such that IE can use it (IE7 introduced a new protected mode, which you can read more about here: http://msdn.microsoft.com/en-us/library/bb250462%28VS.85%29.aspx). So at the same prompt, run the following command:
icacls %userprofile%\AppData\Local\Temp\Low /setintegritylevel low
Having done this, restart IE, and you should find print preview and printing itself now works 🙂 Now I just need to correct the 10 systems I already have setup with this little menace of a problem……
Good luck! 🙂
Make use of the Mac App Store debug menu
Recovering Disk Space on the C: Drive in Small Business Server 2008
http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx
SBS 2008 installs all of its features using a single volume (C:), there are tools available to move some of the data to other locations, but a number of folders that remain in the C: volume can continue to grow if left unchecked, this can potentially eat all the available disk space on the C: drive. Once the C: drive reaches certain low space thresholds, some services will stop functioning properly on the server, while others will change their behavior to prevent data loss. Usually, administrators realize they have a problem when e-mail flow is impacted, under low disk space conditions, due to the Exchange Back Pressure features, mail flow will stop. Users may experience some of the following errors or non-delivery-reports: Error 0x800CCC6C, SMTP_452_NO_SYSTEM_STORAGE, or 452 4.3.1 Insufficient system resources.
These are some of the steps that can be performed to help recover and prevent these issues.
IIS and SBS Logs
(This is expanding on the existing post “Reclaiming Disk Space Lost to IIS Logs on SBS 2003 and SBS 2008”)
By default, all IIS hosted web sites have logging enabled, this can lead to some large folders in C:\inetpub\logs\LogFiles (Review this post in case you have moved your log files). You may also want to specifically stop logging all together for certain web sites, in particular, the “WSUS Administration” web site (Site Id 1372222313). For this, perform the following steps:
- Launch IIS Manager from Administrative Tools.
- Expand Server, Sites, and select the WSUS Administration web site.
- On the feature panel, click to open Logging.
- Click Disable in the Actions panel (rightmost panel)
- Repeat the steps for any other web site. Please note that logging may be needed for troubleshooting or auditing purposes on sites that are public facing, this is usually not the case on the WSUS Administration site.
Some of the SBS 2008 log files can grow to very large sizes, all SBS logs are stores in this folder (and subfolders): C:\Program Files\Windows Small Business Server\Logs\. Some of the logs that will grow the most and may need trimming are:
- Console.log, this log will continue to grow while the SBS Console is running.
- *.evtx files, these are the event logs before the setup of the server completed, they can be safely removed if the server has been in production and had no setup issues.
- W3wp.log, in the C:\Program Files\Windows Small Business Server\Logs\WebWorkplace folder. This is the log for Remote Web Workplace.
- The C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs folder. These are the logs for the Windows SBS Manager service.
POP3 Connector Badmail directory
If you are using the POP3 Connector, you may end up with emails that failed to be delivered (rejected by the local Exchange server) in C:\Program Files\Windows Small Business Server\Data\badmail. This folder will be automatically trimmed to 400mb once it reaches 450mb once a week.
The licensing log can consume a significant amount of hard disk space
This is discussed on the Windows Small Business Server 2008 Release Documentation
You can delete the events in the Windows SBS 2008 licensing log to free up additional space on the hard disk drive.
To delete events in the Windows SBS 2008 licensing log
- From the server, open a Command Prompt window as an administrator. To do this, click Start, and then in the Search box, type command prompt.
- In the list of results, right-click Command Prompt, and then click Run as administrator.
- At the command prompt, type the following command: del "%systemroot%\system32\winevt\logs\Microsoft-Windows-Server Infrastructure Licensing*%4Debug.etl.*"
You can also use Registry Editor to disable the licensing log.
- Click Start, type regedit, and then press ENTER.
- In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerInfrastructureLicensing - In the details pane, right-click TraceMask, and then click Modify.
- In the Edit DWORD dialog box, change the value for Value data to 0 (zero), and then click OK.
- Restart the server.
Windows Server Update Services (WSUS) Server Cleanup Wizard
In WSUS, you can delete unused updates and update revisions, computers not contacting the server, unneeded update files, expired updates and superseded updates. In order to accomplish this, you have to manually go through the WSUS Server Cleanup Wizard.
To run the Server Cleanup Wizard :
- In the WSUS administration console (launch it from the Administrative Tools), select Options, and then Server Cleanup Wizard.
- By default this wizard will remove unneeded content and computers that have not contacted the server for 30 days or more. Select all possible options, and then click Next.
- The wizard will begin the cleanup process, and will present a summary of its work when it is finished, depending on the server performance, this may take a very long time. Click Finish to complete the process.
Very large SharePoint SQL transaction log file
Please read the following KB article for an explanation and instructions on how to prevent this:
2000544 SBS 2008 BPA Reports that The Windows SharePoint Services configuration databases log file is getting large (currently over 1gb in size)
Active Directory Certificate Services transaction log files
When completing a critical or system state backup of the C: volume, a new transaction log will be generated under the c:\windows\system32\certlog\ folder. Removing these logs is only safe as long as the CA database file is consistent. In order to remove these logs and reclaim disk space, follow these steps:
- Open the Services MMC and stop the Active Directory Certificate Services service.
- Make a backup copy of ALL the file contents present in the c:\windows\system32\certlog\ folder.
- Delete EDB.CHK and all the files that have an extension of .LOG (*.LOG)
- Restart the Active Directory Certificate Services service.
Windows Component Clean Tool
The Windows Component Clean Tool (COMPCLN.exe) can be used to remove the files that are archived after Windows Vista SP2 or Windows Server 2008 SP2 is applied. It also removes the files that were archived after Windows Vista SP1 was applied, if they are found on the system. Running this tool is optional.
Installing Windows Server 2008 service packs increases the amount of disk space that is used by the operating system. This space is used to archive files so that the service pack can be uninstalled. Typically, you should run COMPCLN.exe if you want to reclaim this disk space after applying SP2 and if you will not need to uninstall SP2.
NOTE: You cannot uninstall Windows Vista SP2 or Windows Server 2008 SP2 after you run this tool on an image.
Move Data Wizards
We are not going to focus on these wizards on this post, but as a reference, SBS 2008 provides an automated way of moving the following:
- Move Exchange Server Data: which moves both the exchange database file as well as your exchange transaction logs for all storage groups.
- Move Windows SharePoint Services Data: Moves the SharePoint Content and Configuration databases.
- Move Users’ Shared Data: Moves C:\Users\Shares\ directory and all sub directories
- Move Users’ Redirected Documents Data: Moves C:\Users\FolderRedirections\ directory and all sub directories
- Move Windows Update Repository Data: Moves the repository data from C:\WSUS\WSUSContent and C:\WSUS\UpdateServicePackages. Please note it does NOT move the SUSDB Folder and the WSUS database which contains the metadata.
- More Resources:
Manage Server Storage by using Windows SBS Console
Moving Data on Windows Small Business Server 2008
Introducing Server Storage Management in SBS 2008
Update #1 3/3:
Added reference to WSUS Administration web site ID (Site Id 1372222313)
Added reference to Exchange 2007 BackPressure NDRs and errors due to low disk space