Browse by Tags
All Tags »
MSDeploy (
RSS)
In order to enable certain database functionality in the “Refresh” (v1.1) release of the Web Deployment Tool the Web Deploy UI in inetmgr took on a new dependency related to SQL Server Management Objects (“SMO”). In RTW (v1.0) you could do dbFullSql operations in the UI on a remote server when remote managing as long as the remote server had SMO installed, but with Refresh Web Deploy UI, SMO must be installed locally to do dbFullSql operations. Here’s a summary of where you might see errors due to this new dependency or functionality either for local import/export or remote managing of another server along with a breakdown of the errors: Client Web Deploy Version SMO Installed? Server Web Deploy Version Action Symptom Solution RTW Refresh Setting Provider Settings for dbFullSql during Export Provider Settings are blank Install SMO on client RTW Yes (local) Import a package that uses TS Data parameters Parameter entry kind error when you select the package Install Web Deploy Refresh on client...
I was working with one of our partner who want to migrate 30+ sites from an existing IIS6 server, to a new IIS6 server. We had an old tool IIS6 Migration Tool which would come handy, but this would be requiring 30 steps to migrate 30 websites one by one. Here comes the new tool which was specifically targeted for IIS6 to IIS7 migration, but it should help people doing a migration from a old IIS6 to a new IIS6. In this blog, I'm taking a simple scenario where we are going to an offline upgrade. Read the complete post here http://blogs.msdn.com/rakkimk/archive/2010/03/02/msdeploy-can-i-use-it-to-migrate-my-iis6-to-another-iis6-oh-yes.aspx . Read More...
The Web Platform Installer (WebPI) and the Web Deployment Tool (Web Deploy) UI in inetmgr both provide a way for packages to support offering multiple data storage options (such as a choice between SQL and MySQL) in the same package. Package creators can use parameter tagging to access this functionality, which is then surfaced to the end-user as a drop-down choice. WebPI drop-down looks like this: What tags do I use? The current list of data storage options are: SQL Database, MySQL Database, SQLite, VistaDB, and Flat File. Each tag corresponds to a data storage option as noted in the following table for what will appear in the Web Deploy UI: Tag Drop-down option shown Sql SQL Database MySql MySQL Database SQLite SQLite VistaDB VistaDB FlatFile Flat File No Database Note that the “No Database” option will be shown if you use more than 1 database type. How does it work? You may already be familiar with using parameters to customize your application packages. If this idea is new to you, this...
We happy to announce that we just shipped an update to our RTW 1.0 bits with a set of bug fixes that have been reported on the forums and through our feedback channels. What's new: Credential store - no longer do you need to use your password on the command-line, you can get it from the credential store [link coming soon!] Code download update - http://blogs.iis.net/krolson/archive/2010/01/27/code-download-and-the-web-deployment-tool-msdeploy-remote-management-options.aspx TS Data support - http://blogs.iis.net/krolson/archive/2010/02/02/sqlcmd-scripts-in-web-deploy-msdeploy-v1-1.aspx Fixes for a bugs around mime maps, bitness detection and more You can get the new bits at our extension page, http://www.iis.net/webdeploymenttool and in the Web Platform Installer. Happy deployments, Faith and the rest of the Web Deploy team Read More...
New in the v1.1 release of the Web Deployment Tool (MSDeploy) is the ability to deploy .sql scripts which use SQLCMDs such as “:setvar” (a.k.a. TS Data scripts). Additionally, when using such scripts during the import or export of a package in the UI, :setvar variables will be automatically parameterized. Suppose you have a simple script which uses SQLCMD, with contents like the following: :setvar databaseName TestDatabase :setvar tableName TestTable GO create database $(databaseName) GO use $(databaseName) GO create table $(tableName)(name varchar(50)) GO Insert into $(tableName) values('first') Insert into $(tableName) values('first') Insert into $(tableName) values('first') Insert into $(tableName) values('first') Insert into $(tableName) values('first') GO If you try to use this script with the dbFullSql provider to create a database in RTW Web Deploy, you’ll see errors due to the :setvar SQL CMD: Refresh Web Deploy (v1.1) will handle these scripts...
Outlining how the Web Deployment Tool works for remote management using Inetmgr and what has changed between the v1.0 RTW release and the recent v1.1 “refresh” release. What is “code download”? IIS7 (and up) allows you to remotely connect to a server using the IIS Manager (inetmgr) UI and administer it remotely. Sometimes you won’t have all the same components installed on the client box you are using as the server box you are connecting to – code download gives you the opportunity to download client binaries so that you can remotely administer server extensions, even if you don’t have the extensions installed on the client. Code download is a built-in feature in Windows Management Service (WMSvc). When you connect remotely (through WMSvc) to the server, your local inetmgr UI will show you what client binaries are available (i.e. features that support code download and do not exist on the client already) in a “New Features Available” dialog. Does Web Deploy support Code Download? Depends...
The Web Deployment Tool provides a way to delegate application creation to non-Administrator Windows users or IIS users. This blog covers how to configure this particular delegated setting. If you have not yet set up some users, or are not familiar with remote administration, I highly recommend going through this walkthrough: http://learn.iis.net/page.aspx/159/configuring-remote-administration-and-feature-delegation-in-iis-70/ before trying out these steps. Server Admin Steps 1. Install the Web Deployment Tool (MSDeploy) Use the Web Platform Installer (can be found here: http://www.microsoft.com/web/downloads/platform.aspx ) Run and choose Web Deployment Tool 1.0 and click Install. This will also pull in any dependencies you don’t already have on your system. NOTE: This might take a while if you are missing a lot of dependencies (particularly the Windows Installer 4.5 – as this may require a restart) 2. Launch Inetmgr Click Start and type inetmgr. Press Enter. 3. Open Management Service...
This blog outlines the basic steps for setting up IIS Manager accounts so that they may be used for Web Deployment Tool delegation. Most of the steps particular to using IIS Manager users for delegation are required for connecting remotely using the Windows Management service, so if there are already accounts set up for remote management, that work has already been done. The following steps will allow IIS Manager accounts to be used for management service delegation. Step-by-step instructions with screen shots may be found for steps 1 through 4 on this page, with their section title added in parenthesis : http://learn.iis.net/page.aspx/159/configuring-remote-administration-and-feature-delegation-in-iis-70/ 1. Make sure that Windows Management Service is installed ( Configuring Remote Connections in IIS Manager ) 2. Enable remote connections for IIS users ( Enable Remote Connections and Configure Identity Credentials ) The previous steps only need to be performed once, however the following...
This C# code given below will demonstrate how the MSDeploy API can accomplish some common scenarios that users may want to perform. The following examples are documented below in no particular order: I. Server Sync IIS6.0 to IIS6.0 with ‘whatif’,deleting allowed and no content II. Sync with tracing ( verbose is demonstrated ) III. Skip directive usage IV. Replace Rule + Skip Rule ( using skipAction ) usage V. Sync a site from iis7 to Hostable web core ( iis7 ) VI. SetAcl on a directory ( setting provider settings ) If you would like other examples posted or have a request please post below and it could be submitted in the future. I. Server Sync IIS6.0 to IIS6.0 with ‘whatif’,deleting allowed and no content – Setup a server with no content, just the settings and configuration moving from one IIS6.0 box to another IIS6.0 box allowing deletion msdeploy –verb:sync –source:metakey,computername=computer,username=user,password=password –whatif –disableLink:ContentExtension –disableRule:DoNotDeleteRule...
In this blog I will show how to script syncing remote servers and add some useful exception handling. This blog assumes you have read or are familiar with part I at: http://blogs.iis.net/jamescoo/archive/2009/09/09/cool-msdeploy-powershell-scripts.aspx First a borrowed function that will help implement a try catch block in the script-let logic from part I. This will allow for MSDeploy exceptions to be caught and reported making life a bit easier when you get an error. The code is from: http://weblogs.asp.net/adweigert/archive/2007/10/10/powershell-try-catch-finally-comes-to-life.aspx Simply paste this into the Powershell session ( or start all these functions in your profile ) and you are ready to use try catch blocks: function Try { param ( [ScriptBlock]$Command = $( throw "The parameter -Command is required." ), [ScriptBlock]$Catch = { throw $_ }, [ScriptBlock]$Finally = {} ) & { $local:ErrorActionPreference = "SilentlyContinue" trap { trap { & { trap { throw...
More Posts
Next page »