April 2008 - Posts
Body:
If you ever try to install SQL Server 2005 Express Edition with Advanced Services on Windows Server 2008 x64 and receive the following warning during check:
"64-bit ASP .Net is Registered. Required 32-bit ASP .Net to install Microsoft Reporting Service 2005 (32.bit)"
Run following command:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
After that if you try to uninstall SQL Server 2005 Express and if you receive this error during reporting services uninstall
The setup failed to read IIsMimeMap table. The error code is -2147024893
simply stop default web site prior SQL uninstall.
Category: Sharepoint
Published: 30.4.2008 20:31
Body:
If you are thinking to migrate your network environment to Windows Server 2008 and planning to use maybe Exchange 2007 or other IPv6 "aware" products be careful not to disable IPv6. Instead use some online IP converter to recalculate your IPv4 to IPv6.
Here is my recomendation:
Category: Windows Server
Published: 30.4.2008 9:34
Body:
If you are lookin for a way how to purge disconnected mailbox from Exchange 2007 from Exchange
Management Console you in for a big surprise because only way to do it is by using shell. Exchange Server 2007 doesn't allow you to purge the disconnected mailbox and in order to remove single or multiple disconnected mailboxes you can do following:
Get all disconnected mailboxes
Get-MailboxStatistics | where-object { $_.DisconnectDate -ne $null } | Select DisplayName,MailboxGuid
Remove a single disconnected mailbox
Remove-Mailbox -Database <Database-Name> -StoreMailboxIdentity <MailboxGuid> -confirm:$false
Remove all disconnected mailboxes
$users = Get-MailboxStatistics | where-object { $_.DisconnectDate -ne $null } | Select DisplayName,MailboxGuid,Database
Now, all disconnected mailboxes are in a variable and you need to run following cmdlet to remove all of them:
$users | ForEach { Remove-Mailbox -Database $_.Database -StoreMailboxIdentity $_.MailboxGuid -confirm:$false }
Category: Exchange
Published: 30.4.2008 9:17
Body:
Recently we have come into a project that demanded us to implement an Active Directory driven logging mechanism in Windows Sharepoint Services with Forms Based Authentication. The problem took some research and hacking around with some XML but we tackled it pretty quickly.
This text 
on MSDN helped us out a lot so you should take it as a good read. Creating a WSS site is a clear-cut case, we enabled anonymous access so everyone can get to is and supplied the “ADProvider” as a Membership provider name. Then you need to edit the web.config document of the site you created (in IIS > root of the site).
Before the <system.web> tags you need something like this.
This will point to your container with user accounts.
Inside the <system.web> and after the <authorization> tags you need to specify your connection.
<membership defaultProvider="ADProvider">
<providers>
<add name="ADProvider" type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
connectionStringName="ADService"
connectionUsername="domain\administrator"
connectionPassword="password" />
</providers>
</membership>
Now fire up your favorite browser and go to your site, go into the login area and attempt to login with your username (
user@domain.com) and password.
You should be up and running now.
Category: Sharepoint
Published: 29.4.2008 14:02
Body:
Recently I've found that when connecting to some computers trough Windows Vista remote desktop (on LAN), connection was sooo slow that it was unusable. Actualy problem is within Vista network interface autotunning, and simple netsh command disabled the feature, and after that RDP was fast once again.
If you are experiencing similar issue, open command prompt and type:
netsh interface tcp set global autotuninglevel=disabled
For more information visit http://blogs.msdn.com/wndp/archive/2007/07/05/receive-window-auto-tuning-on-vista.aspx
Category: Windows Server
Published: 29.4.2008 14:02
Body:
Finally, for those of you that have waited for solution here is solution for login problem between Vista and Sharepoint 3.0.
With Office 2007 running on Windows Vista, opening an Office document hosted on a SharePoint 3.0 site results in a prompt for login credentials even if the user is already logged on with an account that has access to the document. Canceling the credential prompt may still (but not always) allow the document to open in read-only mode.
Works like charm :)
Category: Sharepoint
Published: 29.4.2008 14:01
Body:
To test this, try to add a database to the Recovery Storage Group, and if the Exchange System Manager program crashes then the answer to this post title is YES, Specifically, this symptom occurs when the Microsoft Office Live Communications Server (LCS) 2005 Administrator tools and Microsoft Exchange Server 2003 are installed on a same computer.
Also, you can try to preview the users of Default Global Address List (Exchange System Manager > Recipients >All Global Address Lists > Right Click Default Global Address List > Click Preview) and if it fails with Active Directory Extension failed (check for maildsmx.dll and Lcdsuiex.dll in event log) you could resolve this by following solutions:
Btw, second one solved my problem, eventhough I got the hotfix from Microsoft support.
Category: Exchange
Published: 29.4.2008 14:01
Category: Exchange
Published: 29.4.2008 14:01
Body:
Finally Exchange 2007 SP1 (Final) is here. As I wrote in first article there is a list of many new features that are implemented in SP1. Download it at http://www.microsoft.com/downloads/details.aspx?FamilyId=44C66AD6-F185-4A1D-A9AB-473C1188954C&displaylang=en
Improvements in Exchange Server 2007 SP1 include:
Anywhere Access
- Integrated Exchange Unified Messaging functionality with Microsoft Office Communicator 2007 and Microsoft Office Communications Server 2007.
- Outlook Web Access additions, including public folder access, S/MIME support, personal distribution lists, and mailbox rules editor.
- Webready document viewer supports Microsoft Office 2007 documents in addition to Microsoft Office 2003 documents.
- Extended language support in Outlook Web Access with Arabic and Korean spell checking.
Operational Efficiency
- Support for Windows Server 2008 deployments, including benefits in flexible clustering, advanced networking, and simplified management.
- Additional tools in the Exchange Management Console, including public folder management and configuration options for clustering and POP/IMAP access.
- Improvements to the Exchange Management Shell syntax and import-export PST in the move-mailbox command.
- Wider variety of web services for application development, including public folder access, delegate management, and folder level permissions.
Built-in Protection
- Addition of Standby Continuous Replication (SCR) for site resilient high availability deployments.
- Extended Exchange ActiveSync policies for mobile policy enforcement.
- Information rights management pre-licensing by the Hub Transport role.
- Secure Real Time Protocol (SRTP) support in the Unified Messaging role.
- Support for IPv6 when using Windows Server 2008.
Category: Exchange
Published: 29.4.2008 14:00
Body:
Recently I stumbled upon problem while instaling Exchange 2007 SP1 on Windows Server 2008, that resulted in delayed start of Microsoft Exchange Transport Service. After several minutes of retrying to start this service, setup failed and Error 2114 was logged in application log
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1712). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
After browsing for solution I have figured it out. Problem was with disabled IPv6 on the network adapter. This seems to prevent the correct topology resolution. By simply enabling IPv6 on the adapter all services were able to start.
After that all you need to do is re-run the Exchange Setup again in Maintainance mode and add missing fetures.
Category: Exchange
Published: 29.4.2008 13:59
Body:
If you’re running Windows SharePoint Services 3.0 on server farm, and adding new server, you can automatically update software and version to match the rest of the servers in your server farm.
In order to do this it’s recommended that you use the Updates folder feature to create an installation source that contains the software updates files.
To create this installation source you must copy the following files, which are included in the Windows SharePoint Services 3.0 Service Pack 1 package, to the Updates folder:
- stswwsp1.msp
- wsswwsp1.msp
- wssmuisp1-en-us.msp
- wsssetup.dll
The file supplementaleula_wss_en-us.txt will also be extracted but does not need to be included in the Updates folder.
Use the following procedure to create an installation point that contains the software update files.
To use the Updates folder:
- Download the appropriate software update package.
- To extract the software update files, use the command <package> /extract:<path>. The /extract switch prompts you to provide a folder name to which to extract the files. For example, for x86 systems:
Wssv3sp1-kb936988-x86-fullfile-en-us.exe /extract:C:\WSS\Updates
where C:\WSS is the location where you have previously copied the Windows SharePoint Services 3.0 released version.
- Copy the extracted files to the Updates folder in the location where you previously copied the source for the released version. You can now use this location as an installation point, or you can create an image of this source that you can copy to a CD-ROM disk.
more info available at http://technet2.microsoft.com/windowsserver/WSS/en/library/91649a7e-6b5a-4e5a-9ee5-51951f4b857f1033.mspx?mfr=true
Category: Sharepoint
Published: 29.4.2008 13:59
Body:
Is set of comprehensive guidance and tools from Microsoft to optimally deploy Windows Vista and the 2007 Office system
This solution accelerator provides tools that enable IT professionals to:
- Create a software and hardware inventory to assist in deployment planning.
- Test applications for compatibility and mitigate the compatibility issues discovered during the process.
- Set up an initial lab environment with deployment and imaging servers.
- Customize and package applications.
- Automate desktop image creation and deployment.
- Ensure that the desktop is hardened to improve security within the environment.
- Manage processes and technologies to produce a comprehensive and integrated deployment.
BDD contains guidance, sample templates, and technology files (such as scripts and configuration files). It presents deployment guidance as feature team guides that thoroughly explain each deployment process.
More info and download is available at http://technet.microsoft.com/en-us/library/bb490308.aspx
Category: Windows Server
Published: 29.4.2008 13:58
Body:
If you can't live without MCPBLOG site (as if) here is a neet feature of this blog. Many of you have probably figured it out that this blog is based on Windows Sharepoint Services 3, and they have out of box feature called mobile view.
To see this web site via GPRS/EDGE enabled phone just visit
www.mcpblog.net/m and enjoy :)
Category: Sharepoint
Published: 29.4.2008 13:58
Body: After I've installed two language packs in addition to Microsoft Office SharePoint Server 2007 (later I found that this can be also applied to WSS 3.0) I tried to open the help window for that language. When I click Help, following error message appeared:
Cannot display help. Technical details: HC not found. (Manifest , LCID)
There may be two solutions to this issue:
Solution 1
This issue occurs because SharePoint Server 2007 has not completed the installation of the help collections. The job may be queued by the SharePoint Job Timer
Solution 2
If the previous procedure does not resolve the issue, directly install the help collections. To do this, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, type the following command, and then press ENTER:
cd %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\BIN
- At the command prompt, type the following command, and then press ENTER:
Hcinstal.exe /act InstallAllHCs
- After you run the command, you are presented with a return code that shows the result of the operation:
- Return code 4 means that the operation was successful.
- Return code 32 means that no action was taken.
- Return code 256 means that the operation failed.
Category: Sharepoint
Published: 29.4.2008 13:57
Body:
You have spent noumerous hours bowsing throug your PocketPC device searching for option to change "working hours" in the calendar. It there a easy way? No! You need to tweek your registry. (www.resco.net for registry)
Default value for 8am-5pm:
HKLM\Software\Microsoft\Calendar\ActiveTimes\ActiveTimes = 2210003E (DWORD hexadecimal)
For 9am-5pm:
HKLM\Software\Microsoft\Calendar\ActiveTimes\ActiveTimes = 2212003E (DWORD hexadecimal)
For 2pm-10pm:
HKLM\Software\Microsoft\Calendar\ActiveTimes\ActiveTimes = 2C1C003E (DWORD hexadecimal)
The first 2 characters define the ending hour as a count of half hours since midnight, in hexadecimal. So for midnight, it would be 0 half hours in hexadecimal = 0. 5pm is 17 hours, or 34 half hours. 34 in hexadecimal is 22. 10pm is 22 hours, or 44 half hours. 44 in hexadecimal is 2C. You can use a calculator capable of hexadecimal conversions to get the hexadecimal number.
Similarly, the next 2 characters define the starting hour as a count of half hours since midnight, in hexadecimal. So for 8am.. 16 half hours, 16 in hexadecimal is 10. 9am = 18 half hours = 12. 14h = 28hh = 1C.
Using the above, you should be able to se the working hours to whatever you'd line. Note that this value also adjusts the working DAYS. The examples here all use the default Mon-Fri workweek. See the "Change Calendar 'working days'" tweak to modify this. Note that the ActiveDays key and value may not exist. Simply create them first. Note that you cannot set the End time earlier than the Start time, for obvious reasons. Note that you cannot set a Midnight end time. The best you can do is 11.30pm (2F).
More tweeks can be found on http://www.freddyreyes.com/forums/index.php?topic=120.5;wap2
Category: Pocket PC
Published: 29.4.2008 13:57
More Posts
Next page »