Ah thats because IIS needs at least 1 site in place. It stupidly looks for the Id of the newest created site and then adds 1 to it to get the new Id. If ano site exists, then it throws a wobbly  


On Sunday, 20 October 2013 at 01:10, Bryce Catlin wrote:

> In manifests/manage_site.pp:
> > @@ -16,8 +16,12 @@ > require => [ Iis::Createpath["${site_name}-${site_path}"], Iis::Manage_app_pool[$app_pool] ], > } > } else { > + if ($site_name == 'Default Web Site') {  
> I deleted it while testing and wasn't able to use power shell to add any site again. Some funky error about bad indices I think. But if you feel strongly I can remove those 3 lines. Bryce, from my iPhone, please xcuse speling mistaks On Oct 19, 2013, at 5:08 PM, "Paul Stack" <notifications@github.com<mailto:notifications@github.com>> wrote: In manifests/manage_site.pp:
> @@ -16,8 +16,12 @@ require => [ Iis::Createpath["${site_name}-${site_path}"], Iis::Manage_app_pool[$app_pool] ], } } else { + if ($site_name == 'Default Web Site') {
> Why is this the case? If the user wants to delete the Default Web Site then why stop them? - Reply to this email directly or view it on GitHub<https://github.com/opentable/puppet-iis/pull/12/files#r7081008>.
>  
> —
> Reply to this email directly or view it on GitHub (https://github.com/opentable/puppet-iis/pull/12/files#r7081013).
>  
>  
>