Deployment Solution

Hi Shawn,

Did you get solution to this error if VBScript runtime error: File already exists".. as i am facing the same issue .

Thanks

This sound quite wierd to me. The thing is that since the GUID is the same - then the package is the same for both SMF and PS, and they both should download it the same way. If PS has downloaded this package to own "Cache" folder below GUID folder, then SMF should do the same way, since they both are using the same core engine of "Package Delivery".

For other packages - it depends, since if package on NS has the "Package Destination Location" defined to some custom path, then the package binaries (the "Cache" folder with content) will be created at this defined location, and default location will contain only "codebases" (usual 3 xml files).

Hi Roman,

 Thank you so much for sharing this valuable information with us, this will help everyone to better understand how the PS works, and it is a great help for troubleshooting as well.

Regarding this info.

"So if you don't have the folders "Cache" and "web" under "Software Delivery" folder, that means the SMF did not download the package yet by some reason. In this case you could check the SMA logs to see the reason and/or press "Download" link on the left side menu when package is selected, in order it to try downloading it once again"

 The interesting thing is that if you check on the SMA under Software delivery tap, you can see that the package has been downloaded, although when you check the "software delivery" folder you only have the usual 3 xml files but the cache folder is missing.

 We have noticed this is also happening with some other packages.

P.S. we are seeing the behavior in 7.5 SP1 HF5    

Ruben

Best regards,

Hi guys!

I don't have any knowledge regarding the DSPS, but here are some clarification to your comments regarding packages and the Package Server:

The path "C:\Program Files\Altiris\Altiris Agent\Package Delivery" is the default package repository for Package Server.

The path "C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery" is the default package repository for Software Management Framework (and SM Agent).

So if package come to a Package Server, then it goes to "Package Delivery" folder. If package come through the upgrade/roll-out/MSWD/Quick Delivery policy then it goes to SMF agent and it is placed to the "Software Delivery" folder.

So if you don't have the folders "Cache" and "web" under "Software Delivery" folder, that means the SMF did not download the package yet by some reason. In this case you could check the SMA logs to see the reason and/or press "Download" link on the left side menu when package is selected, in order it to try downloading it once again.

Copying the package by hands is kind of a "hack" workaround.

Regarding the "PS" virtual directory. The PS virtual directory is the pure Package Servers directory and managed by PS codebase. If it is not created, then there could be several reasons:

1. Most probably the PS is not ordered to provide HTTP(S) codebases (pure UNC PS server). In that case go to NS and check "Package Service settings" policy and check that "Publish IIS hosted codebases" is on.

2. Could be that PS do not have enough IIS roles installed, in order to work with IIS. Go to PS and check the logs, whether there are error or warning message like: "...IIS not installed..." or "...virtual directories..." and see what the problem is. If some roles are missing then they will be listed there in the message. Just install missing roles/features and restart the SMA.

3. At the end, the less resource consuming approach to "reinstall" the Package Server (if you don't want to lose PS packages locally and affect the NS, is just to run PS installer with "/reinstall" flag. This will replace the missing binaries etc, just like the MSI installer "Repair" option. Then you could restart SMA. The PS, anyway, will try to check and create (if missing) all of it's Virtual Directories, on each SMA restart.

Hope this helps.

Excellent information Ruben, I really appreciated it.

Hello Shawn, 

I have noticed 3 different scenarios in regard to DSPS, I will try to explain it.

1- The DSPS is not install at all, so you need to install it and then you experience the issue I described in the thread because the "Cache" and "web" are missing from Software delivery\{76D113DE-16D4-4A31-826F-A4DACCEAC8AB}.

Solution: The steps in my first post

2- ( I think this is the one you are experiencing) the DSPS component is installed, but you are missing the "Deployment" virtual directory in IIS ( This virtual directory should be under the PS virtual directory )

Solution: On your site server go to C:\Program Files\Altiris\Altiris Agent\Package Delivery\{76D113DE-16D4-4A31-826F-A4DACCEAC8AB}\cache. In this location you should have a .bat file named "Create_DeploymentDir.bat", run this file from a elevated command prompt and it will create the "Deployment" virtual directory in IIS.

3- This is an scenario I recently saw, and it is a bit trickier, PS is installed and DSPS is installed too, but you are missing de "PS" virtual directory in IIS, therefore the "Deployment" virtual directory in IIS won't be there either as we depend on the PS virtual directory to create the deployment virtual directory.

Solution: I am still researching this, but I would suggest to do the following to uninstall DSPS and PS, then reinstall PS and make sure PS virtual directory is in IIS, and from here install DSPS and use the other solutions if you still face any of the other scenarios.

I understand this solution is not very convenient in some situations, because by removing the PS will force the replication of all your packages over that Site server again, so keep this in mind.

I hope I explained myself clearly.

P.S - Just one clarification, the information above only applies to Site Servers, it does not apply to the Notification Server, as on the Notification Server we do not install the PS and the IIS virtual directories structure is different.

Best regards,

Ruben  

Greetings Ruben,

I followed the instructions in this post because I did not have the  Deployment app installed under the IIS folder on a site server.  I ran the Install_DS_PS_Component.bat file as Admin and received a "Microsoft VBScript runtime error: File already exists" message.   The DS app still does not install.

Any insight on the issue.

Thanks

Hi,

 We have noticed that this might be happening with some other Agents\Plugins as well ( Deployment task server handler), we are still investigating this though.

We will confirm whether this is impacting more Agent\Plugins ASAP.

Best regards

Ruben