Skip to main content

Go Search
Home
About Us
Consulting
Solutions
Case Studies
Our Clients
News
Request Partnership
Request Proposal
Blogs
User Groups
Training
Image Gallery
  

Other Blogs
There are no items in this list.
Home > Blogs

 

How to Install MOSS 2007 on Windows Server 2008
  1. Enable the IIS7 Feature Role on Windows Server 2008 with .NET 3.0. From Control Panel, Programs and Features, Select 'Turn Windows Features On or Off'. Next, Under 'Server Manager, Features' Select '.NET Framework 3.0 Features'. When asked to install the IIS7 role, select yes. Under IIS7 'Security', be sure to select the authentication you want, i.e. Basic, NTLM, Kerberos, etc.
  2. Install SQL 2005
  3. Install SQL 2005 SP2
  4. Download or Insert MOSS 2007 with SP1 on your MOSS front end server. You must use MOSS 2007 with SP1. If you do not have the MOSS media with SP1, the trail version and upgrade the key after install.
    Download MOSS 2007 Trial Edition

    Office SharePoint Server 2007 with SP1 (32 bit)

    http://www.microsoft.com/downloads/details.aspx?FamilyId=2E6E5A9C-EBF6-4F7F-8467-F4DE6BD6B831&displaylang=en

    Office SharePoint Server 2007 with SP1 (64 bit)

    http://www.microsoft.com/downloads/details.aspx?FamilyId=3015FDE4-85F6-4CBC-812D-55701FBFB563&displaylang=en

  5. Run the MOSS 2007 Setup.exe. Enter your product key and click continue:
  6. Read and Accept the License Agreement and click Continue:
  7. For a Farm installation, select Advanced:
  8. Change the Server Type from Stand-alone to Complete. Then click File Location.
  9. On the File Location tab, change the location of the install and data files if you so desire. Then click Install Now.
  10. At the end of the install, click close to end the install wizard and launch the configuration wizard:
  11. Click next to start the Configuration Wizard:
  12. Choose Yes to the warning about starting and stopping services:
  13. Select 'No, I want to create a new server farm' to create a new farm. Then click next.
  14. Specify your SQL database information. If you are using a named instance, be sure to specify this in the database server field with the following format: servername\instancename
  15. Select specify port and enter a port that is easier to remember but above 1024. For example: 10000. Then click next.

  16. Select next to the following screen and MOSS will complete the 9 tasks to setup the configuration. At the end of the 9 steps, you should see a success page where you can click finish.
Error Trying to Protect Document: Cannot use this feature without credentials
Problem
When users try to use Information Rights Management (IRM) with Office 2003/2007, they might received the following error:
"Cannot use this feature without credentials."
An IRMCheck shows the following warning:
9. User certificates WARNING No user certificates found.
However, browsing directly to the certification web service page in IE *works* for the failed user:
If they run the ActivateGIC sample from the RMS SDK or try to get a user certificate programmatically, they might get the following error:
0x8004CF43 (E_DRM_AUTHENTICATION_FAILED)
And looking in the Application Event Log on the RMS server shows no RMS warnings or errors when the user tries to get a certificate.
 
Resolution
Chances are someone made a change to the IIS server that is hosting RMS and changed the authentication method to Anonymous access. Check the authentication method in IIS for the following page:
_wmcs/certification/certification.asmx
 
If the authentication and access control properties has "Enable anonymous access" checked, then this confirms the problem. To restore the server, go to the authentication methods for the _wmcs folder. Change the authentication method so that Integrated Windows authentication is the only method checked. Apply the changes. If a dialog box pops up specifying child nodes that have different authentication settings, select all of the nodes and replicate the change to all
sub nodes. Then go back and change the following page with Anonymous access:
_wmcs/certification/activation.asmx
 
This should get back to a default authentication state. Optionally, you can set these other pages to anonymous access (usually done if the customer is trusting passport):
_wmcs/licensing/license.asmx
_wmcs/licensing/publish.asmx

If changing the authentication method back to default does not help and/or the customer's IIS changes goes a lot deeper than just the authentication methods, you should be able to recover RMS back to a default state by removing the RMS server from the SQL ("Remove RMS from this web site") and then adding it back into the SQL ("Add this server to a cluster"). Just make certain that the customer knows what the private key password is for the SLC before disconnecting from SQL. This will be required when trying to attach back to SQL.
Content Filter White Listing in Exchange 2007

By: Chris Russo
Date: July 17, 2008

Recently while working at a client site, I was notified of a report of missing external e-mail messages from a particular sender. Upon further investigation using message tracking in the Exchange Tool Box, I was able to locate the messages which were being quarantined by the Content Filtering agents within Exchange 2007. The following message shows the reason the message were being quarantined.

#550 5.2.1 Content Filter agent quarantined this message ##

Original message headers:

Return-Path: Seth@CatHouseLV.com

Received-SPF: None (Wen-Mail-02.lvpp.local: Seth@CatHouseLV.com does notdesignate permitted sender hosts)


To resolve the issue, I ran the following PowerShell command to bypass the senders' domain from the Exchange Anti Spam agent for Content Filtering.

Set-ContentFilterConfig –BypassedSendersDomains cathouselv.com, crosspromotions.com.au



Verify the setting have been applied by running the following command, notice the bypassed domains circled in red have been added.

Get-ContentFilterConfig | FL



MOSS My Profile Tab Inaccessible - HTTP 404 error
Scenario
Browsed to your MOSS 2007 home page i.e. http://sharepoint
Searched for people (e.g. steve)
Search returned results
Clicked on the user "Steve" in search results
You get HTTP 404 File Not found error message.
Resolution
Check to see if you can access the person.aspx page at http://sharepoint/person.aspx
If not , copy the "Person.aspx" file to the root of web site http://sharepoint from the folder C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\SiteTemplates\SPSMSITEHOST via web folder view in SPD
Customizing Windows PE Level 1

 

Objectives

 

  1. Use the WAIK to create a Windows PE bootable CDRom image
  2. Configure the Boot Configuration Database to boot into Windows PE from a WIM file stored on the local hard disk
  3. Modify Windows PE to include startup actions and scripts
  4. Create a Windows PE image that includes the Recovery Environment
  5. Capture Technician Computer
  6. Deploy Image from network location

 

Scenario

Exercise 1-Create a Bootable Windows PE CD-ROM Which Contains Deployment Tools

Need Windows AIK installed on tect computer

Start > Windows PE Tools Command Prompt > Run as Administrator

 

Create Wim PE directort form AIK

 

Copype x86 c:\WinPE

 

Watch tools get copied from AIK

 

Success

 

Updating path to include peimg, cdimage, imagex

 

C:\Program Files\Windows AIK\Tools\PETools\

C:\Program Files\Windows AIK\Tools\PETools\..\AMD64

 

 

This command will allow you to modify the contents ofWindows PE

 

C:\WinPE>ImageX /mountrw winpe.wim 1 mount

 

ImageX Tool for Windows

Copyright (C) Microsoft Corp. All rights reserved.

Mounting (RW): [c:\WinPE1\winpe.wim, 1] ->

[c:\WinPE1\mount]

 

Successfully mounted image (RW).

 

This command will display packages that are available for installation.

 

C:\WinPE>Peimg /list mount

 

Results

Preinstallation Environment Image Setup Tool for Windows

Copyright (C) Microsoft Corporation. All rights reserved.

 

Listed 15 package(s).

 

PEIMG completed the operation successfully.

 

 

  1. Add desiresd packages

 

Peimg /install=*scripting* mount

 

  1. See added packages

 

Peimg /list mount

 

 

 

 

 

This command copies the deployment tools into the image

 

xcopy "c:\Program Files\Windows AIK\Tools\x86\*.*" mount\ /s

 

This command will optimize the Windows PE image for performance and size

 

Peimg /prep mount

    

This command saves the changes you have made to the WIM file.

 

ImageX /unmount /commit mount

 

This command places the WIM file in the correct place for the ISO creation tool.

 

Copy /y winpe.wim c:\WinPE\ISO\Sources\boot.wim

 

This command uses a provided boot sector and template directory to create a bootable ISO image which will boot the Windows PE WIM file.

 

Oscdimg –n –betfsboot.com iso winpe_custom_x86.iso

 

Start WinPE disk in Technician Computer

 

X:\windows\system32>

X:\windows\system32>cd X:\

X:\ imagex /compress fast /check /scroll /capture c: c:\<image-name.wim> "your comment"

 

About compression

During the compression process, you can select one of the following compression types for your image:

  • maximum

    Provides the best compression. However, it also takes the most time to capture the image.
  • fast

    Provides faster image capture. However, it provides less compression than that provided by maximum. This is the default compression type, used if you leave this option blank or if you use the /capture option without the /compress option.
  • none

    Captures the image without compression.

Because the /compress option specifies the type of compression for your entire .wim file, this option is valid only on the initial capture and cannot be changed. Additionally, if you use the /export option, the source and destination .wim files must have the same compression type.

 

 

after the capture you can save the image to a network share.

 

net use z: \\network_share then copy c:\myimage.wim y:\\network_share\<image folder>

 

 

after copying the captured image you can now then apply it to a new computer:

This step requires booting the new computer with Windows PE and applying the image with ImageX.

  1. Boot the new computer with your Windows PE media.
  2. In Windows PE, format the hard drive using DiskPart.
  3. At a command prompt in Windows PE, map the network drive to your network share. For example,

net use y: \\network_share\images

  1. Apply the image from the network share by using ImageX. For example,

imagex /apply y:\\network_share\images\myimage.wim 1 c:

 

 

 

 

 

Relocating Office Communicator Server 2007 Databases

By: Chris Russo
July 07, 2008

In some cases you might need to move Office Communication Server's back-end database, an example of such a situation would be if the current location has insufficient space available for the database, you can move the back-end database as follows:

Identifying the Current Database Location:

Step 1:

 

Right Click on "Front Ends" and select Properties.

Step 2:

 

On the "General" tab the Back end server address will be listed.


Backup Current OCS Databases:

Step 1:

 

In SQL Server Management Studio "Right Click" RTC, RTCCONFIG & RTCDYN select tasks and "Backup".

Step 2:

 

Verify you have chosen the correct Database to backup, select a "Full" backup, verify the location where you're backup will be written and select "OK".

 

Stopping OCS Services:

Step 1:

 

Stop all Front Ends Services

Step 2:

 

Stop all Web Conferencing Services

Step 4: