# Thursday, 30 March 2006

Backup Companyweb using Smigrate on the source server:

  1. Click Start, and then click Run.
  2. Type CMD and click OK.
  3. In the Command Prompt, type cd %ProgramFiles%\Common Files\Microsoft
    Shared\web server extensions\60\bin, and press ENTER.
  4. Type smigrate -w https://companyweb:444 -f c:\backup.fwp, and press
    ENTER.
  5. Copy the file to the C:\ drive of the second server.


Restore Companyweb using Smigrate on the new server:

  1. On the new server, click Start, point to All Programs, point to
    Administrative Tools, and then click SharePoint Central Administration.
  2. On the Central Administration page, under Virtual Server Configuration,
    click Configure Virtual Server Settings.
  3. On the Virtual Server List page, click the companyweb.
  4. On the Virtual Server Settings page, under Virtual Server Management,
    click Remove Windows SharePoint Services from virtual server.
  5. In the Remove Windows SharePoint Services section, select Remove and
    delete content databases, and then click OK.
  6. Click OK twice to continue.
  7. On the Central Administration page, under Virtual Server Configuration,
    click Extend or upgrade virtual server.
  8. On the Virtual Server List page, click the companyweb.
  9. In the Provisioning Options section, select Extend and create a new
    content database.
  10. On the Extend and Create Content Database page, in the Application Pool
    section, select Use an existing application pool, and then select
    DefaultAppPool (NT AUTHORITY\NETWORK SERVICE).
  11. In the Site Owner section, specify the administrator's e-mail address
    in the E-mail field.
  12. In the Database Information section, uncheck Use default content
    database server, and type STS_ServerName_1 in the Database name field.
    Click OK.
  13. Close the IE Windows when Companyweb virtual server is successfully
    extended. Do not connect to http://companyweb and apply a site template at
    this point.
  14. Click Start, and then click Run.
  15. Type CMD and click OK.
  16. In the Command Prompt, type cd %ProgramFiles%\Common Files\Microsoft
    Shared\web server extensions\60\bin, and press ENTER.
  17. Type smigrate -r -w https://companyweb:444 -f c:\backup.fwp, and press
    ENTER.
  18. When the command is finished, click Start, and then click Run.
  19. Type http://companyweb, and click OK. All the site content should be
    restored.

 


 

sbs
Thursday, 30 March 2006 11:56:01 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback

The question mark indicates that the client user name has not been authenticated. This happens when a request arrives from a Firewall client, but the firewall policy does not require authentication. The Firewall client always sends the user name, and therefore it is always logged.

See: http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/faq-monitoring.mspx

isa
Thursday, 30 March 2006 00:41:34 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Sunday, 26 March 2006

This seems to be post SP1 in Virtual PC 2004...

New guest OSes start with the error:

"The network adaptier with address "00:00:00:00:00:00" of virtual machine <name> failed to initialize becaule the address is a null address"

Two solutions seem to be:

  1. Add "<ethernet_card_address type="bytes">000*********</ethernet_card_address>
    <is_dynamic_assignment type="boolean">true</is_dynamic_assignment>" to the .vmc file, or
  2. Follow suggestion at  http://blogs.msdn.com/virtual_pc_guy/archive/2005/01/17/354971.aspx, shown below.

 

 

Virtual PC SP1 Networking problems (address "00:00:00:00:00:00" failed to initialize)

There have been a number of people reporting that when they start a virtual machine - they get the following error:

The network adapter with address "00:00:00:00:00:00" of virtual machine "...." failed to initialize because the address is a null address.

To fix this problem you should use REGEDIT to:

  1. Examine the key value at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\<nnnn>\DriverDesc to locate the desired host adapter where <nnnn> is a four digit number.
  2. Look at the GUID value for the NetCfgInstanceId key value.
  3. Add the DWORD key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VPCNetS2\Parameters\Adapters\<guid>\Flags and set the value to 0 where <guid> is the GUID found in step 2.
  4. Restart the computer.

This registry value was added in Virtual PC SP1’s Virtual Machine Network Services driver. It is supposed to be setup during installation by the driver’s notify object. However, under certain circumstances the notify object of the old version is used during the installation of the new version and this registry value is never created. It is used by the driver to determine if a particular host adapter can be used in the MAC address generation algorithm. If the key is not present, we assume that the host adapter cannot be. In the case you experienced, none of your adapters appear suitable as a basis for MAC address generation and the driver returns a NULL MAC address which causes VPC to report the error.

Sunday, 26 March 2006 13:05:07 (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Friday, 24 March 2006

After installing this update the new version number (4.0.2165.594) won't appear in the ISA management console configuration dialog (instead it will show SP1 4.0.2163.213).

To find the installed version in the mmc click help->about or go to Add/Remove programs and click "Click here for support information" under the ISA 2004 SP2 item.

ISA Server 2004 rtm: 4.0.2161.50
ISA Server 2004 SP1: 4.0.2163.213
ISA Server 2004 SP2: 4.0.2165.594

isa
Friday, 24 March 2006 09:21:52 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Friday, 17 March 2006

Sometimes being automatically offered the choice to download or open a .pdf is desired.  There are different methods to do this, using Active X, Java, JavaScript and ASP coding.  Here are several different ways to publish pdf files on IIS, some of which giving an open/save choice without and scripting.

Method1 - Embed

Use: <EMBED src="/path/to/file" width="600" height="600" type=application/pdf href="/path/to/file"></EMBED> <NOEMBED>Your browser does not support embedded PDF files.</NOEMBED>

note: works in IE6, Firefox 1.5; add "href=" for netscape

Your browser does not support embedded PDF files. <a href="http://blog.johnkelly.co.uk/ct.ashx?id=26a47232-46ba-4fef-b179-38a112c41883&amp;url=http%3a%2f%2fblog.johnkelly.co.uk%2fcontent%2fbinary%2f13predictions.pdf">Open file by clicking here.</A>


Method2 -

13predictions.pdf (62.89 KB)


Method3 -

download


Method4 -

download-2


Method5 - Object

<OBJECT CLASSID="clsid:CA8A9780-280D-11CF-A24D-444553540000" WIDTH="600" HEIGHT="600">
        <PARAM NAME="SRC" VALUE="path/to/file">
        <PARAM NAME="HREF" VALUE="path/to/file">
        <EMBED SRC="path/to/file" HEIGHT="500" WIDTH="500" HREF="path/to/file">
                <NOEMBED>
                        Your browser does not support embedded PDF files.
                </NOEMBED>
        </EMBED>
</OBJECT>

Note:  Due to a bug in FreeTextBox (DasBlog's native editor) this approach works, briefly, until the post is edited which screws up the EMBED code.

 


Method6 - iframe

 


Method7 - ftp

A link to the file via an ftp site might open the file in the same window, a new window or offer an open/save dialog depending on the browser

 

html | ie | pdf
Friday, 17 March 2006 11:25:28 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback