IIS is typically by default installed and assigned on the system drive C:\inetpub. However you want to move it to D:\intepub. So you start down the whole copy and paste which may seem like it will work however you still have to touch multiple Registry keys and paths. Well here is a simple script to make your IIS moving a snap.

Also if you copy this make sure to name the file a .Bat file for Batch… Just in case.

REM PLEASE BE AWARE: SERVICING (I.E. HOTFIXES AND SERVICE PACKS) WILL STILL REPLACE FILES
REM IN THE ORIGINAL DIRECTORIES. THE LIKELIHOOD THAT FILES IN THE INETPUB DIRECTORIES HAVE
REM TO BE REPLACED BY SERVICING IS LOW BUT FOR THIS REASON DELETING THE ORIGINAL DIRECTORIES
REM IS NOT POSSIBLE.

@echo off
IF "%1" == "" goto err
setlocal
set MOVETO=%1:\

REM simple error handling if drive does not exist or argument is wrong
IF NOT EXIST %MOVETO% goto err

REM Backup IIS config before we start changing config to point to the new path
%windir%\system32\inetsrv\appcmd add backup beforeRootMove

REM Stop all IIS services
iisreset /stop

REM Copy all content
REM /O – copy ACLs
REM /E – copy sub directories including empty ones
REM /I – assume destination is a directory
REM /Q – quiet

REM echo on, because user will be prompted if content already exists.
echo on
xcopy %systemdrive%\inetpub %MOVETO%inetpub /O /E /I /Q
@echo off
REM Move AppPool isolation directory
reg add HKLM\System\CurrentControlSet\Services\WAS\Parameters /v ConfigIsolationPath /t REG_SZ /d %MOVETO%inetpub\temp\appPools /f

REM Move logfile directories
%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/sites -siteDefaults.traceFailedRequestsLogging.directory:"%MOVETO%inetpub\logs\FailedReqLogFiles"
%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/sites -siteDefaults.logfile.directory:"%MOVETO%inetpub\logs\logfiles"
%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/log -centralBinaryLogFile.directory:"%MOVETO%inetpub\logs\logfiles"
%windir%\system32\inetsrv\appcmd set config -section:system.applicationHost/log -centralW3CLogFile.directory:"%MOVETO%inetpub\logs\logfiles"

REM Move config history location, temporary files, the path for the Default Web Site and the custom error locations
%windir%\system32\inetsrv\appcmd set config -section:system.applicationhost/configHistory -path:%MOVETO%inetpub\history
%windir%\system32\inetsrv\appcmd set config -section:system.webServer/asp -cache.disktemplateCacheDirectory:"%MOVETO%inetpub\temp\ASP Compiled Templates"
%windir%\system32\inetsrv\appcmd set config -section:system.webServer/httpCompression -directory:"%MOVETO%inetpub\temp\IIS Temporary Compressed Files"
%windir%\system32\inetsrv\appcmd set vdir "Default Web Site/" -physicalPath:%MOVETO%inetpub\wwwroot
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='401'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='403'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='404'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='405'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='406'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='412'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='500'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='501'].prefixLanguageFilePath:%MOVETO%inetpub\custerr
%windir%\system32\inetsrv\appcmd set config -section:httpErrors /[statusCode='502'].prefixLanguageFilePath:%MOVETO%inetpub\custerr

REM Make sure Service Pack and Hotfix Installers know where the IIS root directories are
reg add HKLM\Software\Microsoft\inetstp /v PathWWWRoot /t REG_SZ /d %mOVETO%\inetpub\wwwroot /f
reg add HKLM\Software\Microsoft\inetstp /v PathFTPRoot /t REG_SZ /d %MOVETO%\inetpub\ftproot /f
REM Do the same for x64 directories
if not "%ProgramFiles(x86)%" == "" reg add HKLM\Software\Wow6432Node\Microsoft\inetstp /v PathWWWRoot /t REG_EXPAND_SZ /d %MOVETO%inetpub\wwwroot /f
if not "%ProgramFiles(x86)%" == "" reg add HKLM\Software\Wow6432Node\Microsoft\inetstp /v PathFTPRoot /t REG_EXPAND_SZ /d %MOVETO%inetpub\ftproot /f

REM Restart all IIS services
iisreset /start
echo.
echo.
echo ===============================================================================
echo Moved IIS7 root directory from %systemdrive%\ to %MOVETO%.
echo.
echo Please verify if the move worked. If so you can delete the %systemdrive%\inetpub directory.
echo If something went wrong you can restore the old settings via
echo     "APPCMD restore backup beforeRootMove"
echo and
echo     "REG delete HKLM\System\CurrentControlSet\Services\WAS\Parameters\ConfigIsolationPath"
echo You also have to reset the PathWWWRoot and PathFTPRoot registry values
echo in HKEY_LOCAL_MACHINE\Software\Microsoft\InetStp.
echo ===============================================================================
echo.
echo.
endlocal
goto success

REM error message if no argument or drive does not exist
:err
echo.
echo New root drive letter required.
echo Here an example how to move the IIS root to the F:\ drive:
echo.
echo MOVEIISROOT.BAT F
echo.
echo.

:success

This should take care of your IIS moving needs. Do not forget to reboot to make sure settings are happy.

Direct Mailer Not working or not sending email or just needs to be configured correctly?

First lets make sure the server and users/groups are created right.

To grant the Marketing Web Service access to the Direct Mailer Service

1. Click Start, point to Programs, point to Administrative Tools, and then click Component Services.

2. In the Component Services window, expand Component Services, expand Computers, expand My Computer, expand DCOM Config, right-click Microsoft Commerce Server DirectMailer Service, and then click Properties.

3. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, in the Launch and Activation Permissions section, select Customize, and then click Edit.

4. In the Launch Permission dialog box, click Add.

5. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <data domain>\MarketingWebSvc, and then click OK.

6. In the Launch Permission dialog box, in the Permissions for <data domain>\MarketingWebSvc section, select the Local Launch and Local Activation check boxes for Allow, and then click OK.

7. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, in the Access Permissions section, select Customize, and then click Edit.

8. In the Access Permission dialog box, click Add.

9. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <data domain>\MarketingWebSvc, and then click OK.

10. In the Access Permission dialog box, in the Permissions for <data domain>\MarketingWebSvc section, select the Local Access check box for Allow, and then click OK.

11. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, click OK

To grant the Marketing Web Service access to the Direct Mailer Service

1. Click Start, point to Programs, point to Administrative Tools, and then click Component Services.

2. In the Component Services window, expand Component Services, expand Computers, expand My Computer, expand DCOM Config, right-click Microsoft Commerce Server DirectMailer Service, and then click Properties.

3. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, in the Launch and Activation Permissions section, select Customize, and then click Edit.

4. In the Launch Permission dialog box, click Add.

5. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <data domain>\MarketingWebSvc, and then click OK.

6. In the Launch Permission dialog box, in the Permissions for <data domain>\MarketingWebSvc section, select the Local Launch and Local Activation check boxes for Allow, and then click OK.

7. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, in the Access Permissions section, select Customize, and then click Edit.

8. In the Access Permission dialog box, click Add.

9. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <data domain>\MarketingWebSvc, and then click OK.

10. In the Access Permission dialog box, in the Permissions for <data domain>\MarketingWebSvc section, select the Local Access check box for Allow, and then click OK.

11. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, click OK

And verify that your web service identity is a member of the DML_SG group

Prepare the Members and Groups for COM component Services:

Member Manage:

Create the group DML_SG

Add the following users to the:

DML_SG

CSDMSvc

MarketingWebSvc

Add the following users to the:

MarketingAdminGroup

RunTimeUser

MarketingWebSvc

CSDMSvc

Add the following users to the:

Administrator

MarketingWebSvc

Go into services and make sure commerce server direct mailer is running and set to automatic.

Trouble Shooting

You can add the following registry change if these do not work.

Open Registry using regedit.exe.

Navigate to HK_LOCAL_Machine\Software\Microsoft\SchedulingAgent and give full control to NT account under which marketing system is working (or add authenticate users).

*Right click on the key and scroll down to permissions inside permissions add DML_SG and give full permissions.

Test Emailing by scheduling a DML run with dmlrun.exe:

dmlrun.exe /create:type=final;site="Buylifetime.com";id=30 /execute

If that doesn’t work, try using the DirectMailer COM object to test your direct mail:

Dim dm

set dm = CreateObject("Commerce.DirectMailer", "<DML Server Name>")

call dm.TestDirectMail("StarterSite", 30)

save and do IIS reset

Last and most effective:

Open a Command Prompt go to (different for 32 and 64 bit servers(Provided is the 64bit version))) C:\Program Files (x86)\Microsoft Commerce Server 2007 Then run:

csconfig /r Feature.MS.CS.DirectMailer

Recently I have had the pleasure of making Commerce Server 2007 run (play nice) with Windows Server 2008r2. This was interesting in many many ways to which I will document down the road.

For this post I wanted to share a great little script that helps with your own or the default “PUP” install.

As those of us that have installed Commerce Server 2007 on multiple machines architectures and what not know when installing the “PUP” it is important to keep the “default” web site intact. Also if you can help it, Not to have any other sites running or created in IIS6 – IIS7.5. However you may have some installed and the APP ID’s all randomized (default behavior for IIS (all versions)). The “PUP” installer may have issues with “other” web sites running in IIS.

So to check what may be causing these issues try running my happy little script.

Put the following code into a vbs and run.

‘The code below simulates Commerce Server Site Packager checking IIS health.
‘This IIS checking happens when you click the "next" button at the first dialog of the Site Unpacking
‘This code helps you to find out where the checking fails

set oNet=CreateObject("WScript.Network")

sLocalMachine = oNet.ComputerName

Set webServer = GetObject("IIS://" & sLocalMachine & "/w3svc")

msgbox "Web Server "+ sLocalMachine +" has the following Web Sites:"
For Each webSite In webServer
        If IsNumeric(webSite.Name) Then

            sName = webSite.Name
        msgbox "Web Instance Number: "+sName

            sComment = webSite.ServerComment
        msgbox "Web Site Name: "+sComment

            Foo = webSite.ServerBindings
        msgbox "Port "+Foo(0)

            Set vroot = webSite.GetObject("IIsWebVirtualDir", "Root")
        msgbox "Root: "+vroot.path
        End If
Next

set onet=nothing
set webserver=nothing
set webSite=nothing
set vroot=nothing

Enjoy! Let me know how it goes.

IIS7.5 is a beautiful web server. Not to the naked eye (gangster Geek term for Non-Geek) but for the web master that loves Apache, Tomcat or IIS * (anything for the non-geek) and of course we wont speak of those other wanna be web server software’s out there and you know who you are please go away.

*Now off the soap box*

Anyway the IIS7.5 Gui is pretty and fun. However looks don’t mean much unless you have brains. So back to the whole setup and why this post is being written.

Setting up FTP is kind of a chore in IIS7.5. Why I say that is it offers some really awesome features (yes I will spare you the details) FTP has security features that allow it to be an easier setup than in any other IIS version. 

Alright so the long and the short of this post is how to setup IIS7.5 to use Isolation mode.

First use a ftproot type folder: C:\inetpub\ftproot will do.

Run this from the command line: “ICACLS “C:\inetpub\ftproot” /grant IUSR:R”

Now under that folder create a folder called LocalUser *make sure to pascal case sensitive (this according to M$)

Then Create a folder called “Public” then create a local user for example: Administrator

Now point your FTP root directory to the C:\inetpub\ftproot

FTP will then pick up and understand that is the directory and will use the appropriate folder setup

When you try to connect to the Ftp using a certain username FTP will Isolate the folder for you.

This is awesome. enjoy your new FTP site.

Flash (flv)

If you are a Adobe geek and use IIS6 and you cannot fiqure out why a .FLV file will not render or you get the evil 404.3 error. Try this:

Flash Streaming MIME:
flv
extension: .flv
MIME type: flv-application/octet-stream

To add the MIME types to IIS6:

1. Choose your website in IIS
2. Open the context menu and choose "Properties"
3. Select the register "HTTP-Header"
4. Click on the button labeled "MIME Types…"
5. If .flv is not yet listed as a type, choose "New"
6. Enter the following description:
Extension: .flv

MIME type: flv-application/octet-stream7.

7.Click "Ok",
8. Choose "Apply" and you’re set!

Silverlight

If you want to host Silverlight on a web server that isn’t IIS7, such as IIS6 which is the second best web server in the world (2nd to IIS7 ) you’ll need to add the MIME types to support the correct content type interpretation by the browser. In the case of Silverlight this is the XAML content type – this also goes for WPF hosting as well. IIS7 has these MIME types already added but if they’re not there this will result in errors such as 404.3 and prompting to download etc.

There are 3 MIME types required

Summary: This document provides tables that illustrate, for a range of IIS authentication settings, the resultant identity that is obtained from each of the variables that maintain an IPrincipal and/or IIdentity object. (4 printed pages)

Principal objects implement the IPrincipal interface and represent the security context of the user on whose behalf the code is running. The principal object includes the user’s identity (as a contained IIdentity object) and any roles to which the user belongs.

ASP.NET provides the following principal and identity object implementations:

• WindowsPrincipal and WindowsIdentity objects represent users who have been authenticated with Windows authentication. With these objects, the role list is automatically obtained from the set of Windows groups to which the Windows user belongs.
• GenericPrincipal and GenericIdentity objects represent users who have been authenticated using Forms authentication or other custom authentication mechanisms. With these objects, the role list is obtained in a custom manner, typically from a database.
• FormsIdentity and PassportIdentity objects represent users who have been authenticated with Forms and Passport authentication respectively.

The following tables illustrate, for a range of IIS authentication settings, the resultant identity that is obtained from each of the variables that maintain an IPrincipal and/or IIdentity object. The following abbreviations are used in the table:

• HttpContext = HttpContext.Current.User, which returns an IPrincipal object that contains security information for the current Web request. This is the authenticated Web client.
• WindowsIdentity = WindowsIdentity.GetCurrent(), which returns the identity of the security context of the currently executing Win32 thread.
• Thread = Thread.CurrentPrincipal which returns the principal of the currently executing .NET thread which rides on top of the Win32 thread.

Note   With IIS 6.0 running on Windows Server 2003, the identity Matrix works except that the Machine\ASPNET identity is replaced with NT Authority\Network Service.

IIS anonymous authentication

IIS basic authentication

IIS digest authentication

IIS integrated Windows

use MSCS_Admin
select s_PropertyName, s_Value
From dbo.resourceProps

This will return multiple values. This is helpful in knowing if you have Commerce Server 2007 installed correctly as well as helping you to identify the correct service pack upgrade number per database.

SP1

Transaction Database = 7.0

Transaction Config Database = 7.0

Product Catalog Database = 7.2

Inventory Database = 7.1

Direct Mailer Database = 6.0

SP2

Transaction Database = 7.1

Transaction Config Database = 7.1

Product Catalog Database = 7.3

Inventory Database = 7.2

Direct Mailer Database = 6.0

Enjoy!

@echo off

    :start
    set /p _input="Server? [y/n]"

    if %_input% equ y (
        echo Starting server services…
        sc start HTTPFilter     REM HTTP SSL
        sc start IISADMIN        REM IIS Admin
        sc start lanmanserver    REM Server
        sc start MSSQLSERVER    REM SQL Server
        sc start SQLBrowser        REM SQL Server Browser
        sc start SQLWriter        REM SQL Server VSS Writer
        sc start W3SVC            REM World Wide Web Publishing
        sc start WebClient        REM WebClient

        set /p ="Hit any key to continue…"
    ) else (
        echo STOPPING server services…
        sc stop HTTPFilter
        sc stop IISADMIN
        sc stop lanmanserver
        sc stop MSSQLSERVER
        sc stop SQLBrowser
        sc stop SQLWriter
        sc stop W3SVC
        sc stop WebClient

        set /p ="Hit any key to continue…"
    )

    :end

Things hang or people want their email better formatted. Or simply test out you spam messages you are going to blast before you well blast them.

Of course you run into issues like is my ports open correctly, is the SMTP server setup to block relaying? Has my domain been blacklisted from spamming?

These kind of questions are important. While I can’t fix the blacklisting domain issue the rest is well my night job.

However during the day I develop lots and lots of web code and sometimes and most often these applications need a way to contact people via email, txt and so forth.

Being behind a great firewall and sending test email can be a long and drawn out process. I found a  great application to do the SMTP testing for you inside you own localhost(127.0.0.1) Yes that is my localhost ip if you would like to “hack me” go ahead Ill wait.(if you don’t already know that is the IP of your pc).

PaperCut

This little app allows you to send SMTP messages without sending them anywhere.

Paper Cut is my favorite application for development. It allows me to debug the smtp messages without sending them to anyone.

Do you want it now and free? 

Check this little app out.

It comes from our friends at niknak.org.

niknak.org – IIsTrafficMonitor