I'm having a problem deploying office 2010 to machines in our environment.

The application seems to deploy perfectly to windows 7 as part of the build process but deploying to windows XP machines is causing me a headache.

 

The client will start the download, it will then hang at a random percentage.

DatatransferService.log shows reoccurence of these 2 lines:

 

<![LOG[CDTSJob::HandleErrors: DTS Job '{19F0A849-711F-499C-9A43-46B35568B7E0}' BITS Job '{EC5A3A95-45E3-42F6-9C53-03264063A240}' under user 'S-1-5-18' OldErrorCount 298 NewErrorCount 299 ErrorCode 0x80072EFE]LOG]!><time="18:08:07.147-60" date="09-11-2012" component="DataTransferService" context="" type="2" thread="2760" file="dtsjob.cpp:4527">

<![LOG[CDTSJob::HandleErrors: DTS Job ID='{19F0A849-711F-499C-9A43-46B35568B7E0}' URL='http://servername:80/SMS_DP_SMSPKG$/Content_98740ce7-8e1c-4f66-b918-dd487f3bb202.1' ProtType=1]LOG]!><time="18:08:07.147-60" date="09-11-2012" component="DataTransferService" context="" type="1" thread="2760" file="dtsjob.cpp:4540">

 

 

I've checked the IIS logs on the Deployment Point for this client and for each download attempt I see this:

2012-09-11 17:10:46 10.2.1.34 GET /SMS_DP_SMSPKG$/Content_98740ce7-8e1c-4f66-b918-dd487f3bb202.1/sccm /ProPlus.WW/ProPlusWW.msi 80 DOMAIN\PC603$ 10.2.12.182 Microsoft+BITS/6.7 206 0 64 19378

2012-09-11 17:11:46 10.2.1.34 GET /SMS_DP_SMSPKG$/Content_98740ce7-8e1c-4f66-b918-dd487f3bb202.1/sccm /ProPlus.WW/ProPlusWW.msi 80 - 10.2.12.182 Microsoft+BITS/6.7 401 2 5 0

 

I've checked the authentication on the SMSPKG$ site and it's set to only have Windows Auth enabled.

The 401.2 error is a Unauthorized: Logon failed due to server configuration

 

There are no firewalls on the client or the DP server, as far as I can see boundaries are correct. I was wondering if anyone had any suggestions on where to look next?

When is this occuring? Through OSD or from within windows? Are you using SCCM 2007 or SCCM 2012?

 

Thanks

This happens either from Software Center or as a Deployment. I'm using SCCM 2012

Have you tried running from the ditribution point and copying local and then running, both should be flags on the package / program, i had an instance where this was happening to me during osd specifically and the fix was to have the software installation taks copy the files local first and then execute.

It is set to download content, the problem is the content never downloads, it always hangs downloading ProWW.msi

Have you tried just running it from the distribution point? I ussually had hanging issues like that if files were sometimes corrupt. You could try copying the file from the source media and redistributing your source files to see if that changes anything.

 

Thanks

It is set to download content, the problem is the content never downloads, it always hangs downloading ProWW.msi

If your client on AD ,Please check your boundary and boundary Groups

if your client on workgroup,please try to run it from distribution point before copying it to local and then running

Sorry for the delay, been on holiday!

The client is AD related.

Boundaries are configured as follows:

We have 10 boundaries, 8 IP address ranges, 2 subnets. The clients that I'm working on at the moment are in the 10.2.102.x subnet which is part of the boundary for our head office. That is configured as an address range of 10.2.0.0-10.2.255.255

That range as well as the remaining 9 boundaries are all in the only configured boundary group.

 

The content starts to download but always hangs at ProWW.msi, that can be a random percentage but it's always the same file and that file will download perfectly to a machine being built by OSD and a windows 7 machine on the same subnet as the Deployment Point.

Have you tried creating the office package again?

 

What space is left on the client cache on the XP machines maybe it is full??

 

Rocket Man

Office package has been recreated.

Client cache has 5gb free and the harddrive has more than 100gb free.

If I move the client onto the same subnet as the distribution point then the package installs correctly.

There is something preventing the download of proww.msi if the client is on a different subnet.

I'm just about to try a vanilla built windows 7 machine on different subnets to the DP and see if that can deploy.