.Net 3.0 Administrative Setup

[Guest]

..Net 3.0 deployment via Active Directory and Group Policy seems pretty broken
to me. The most up to date info I can find is in the RTM SDK under
'Microsoft .NET Framework 3.0 Administrator Deployment Guide'.

The script at the bottom of that article ignores the WIC and XPS components
of dotnetfx3.exe and the command to extract wcf.exe does not work. WCF.exe
/? indicates there is no /c switch for wcf.exe.

Could someone from MS have a look at this and provide a working script or
other instructions on how to deploy with Group Policy?

Thanks
Michael

 

[Gary Chang[MSFT]]

Hi Michael,

The script at the bottom of that article ignores the WIC and XPS
components of dotnetfx3.exe and the command to extract wcf.exe
does not work. WCF.exe /? indicates there is no /c switch for wcf.exe.

The WIC is not the .NET Framework 3.0's components, it is the Microsoft
Windows Systems Components, the general convention to install the component
is via the Windows Update(Optional). So the NET Framework 3.0 doesn't
contain this component. If you want to install it as command line, you can
download that component package from the following link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=8e011506-6307-445b-
b950-215def45ddd8&DisplayLang=en

Then you need to extract its exe file and run the update.exe (in ite update
subfolder) as the following, this Windows update may need a reboot to take
effective:

update /q /norestart

Please refer to the following MSDN article links for the details about how
to run the update.exe from the command line:

The Package Installer (Formerly Called Update.exe) for Microsoft Windows
Operating Systems and Windows Components
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/deployment/wi
nupdte.mspx


The XPS should be already been integrated in the core components of the
..NET Framework 3.0, it is not provided as a separated component in .NET
Framework 3.0's redist package.


For the issue about the command to extract wcf.exe, I am afraid that .NET
Framework 3.0 Administrator Deployment Guide makes a mistake here. The
corresponding component installation package for the WCF is indigo.exe
(Indigo is the codename of the WCF), there is no wcf.exe is the .NET FX
3.0's package, you just need to replace the wcf.exe with the indigo.exe in
the corresponding line of the script. We are sorry for the inconvenience
which that mistake brought to you.

By the way, the sample script in that Deployment Guide article would
install all the NET Framework 3.0 components administratively, except for
the bug of that non-existed wcf.exe.


Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Hi Gary,

Sorry for not picking up on this. I got rather distracted by Vista RTM and
repaving my development machine.

Firstly, you say WIC is not part of the .NET 3.0 redistributable but it
looks to me as if it is.
Following the script from the SDK 'Microsoft .NET Framework 3.0
Administrator Deployment Guide' I start by extracting the files from
dotnetfx3.exe using:-

set WORKFOLDER=c:\deploy
call dotnetfx3.exe /q /x:C:%WORKFOLDER%\ext

This produces subdirectories for all the .Net 3.0 components which include
WIC and XPS. The WIC directory contains WIC_X86_ENU.exe and the XPS
directory contains XPSEPSC-x86-en-US.exe. Neither of these are installed by
the script in the deployment guide.

Also, the WCF subdirectory contains wcf.exe - not indigo.exe. The
deployment script suggests that the following will produce an .msi that I can
use for an administrative install:-

call %WORKFOLDER%\ext\wcu\WCF\wcf.exe /q /c:"msiexec /qb /a wcf.msi
REBOOT=ReallySuppress /l* %WORKFOLDER%\logs\WCF_x86.log
TARGETDIR=%WORKFOLDER%\AIP\WCF_x86"

- but it doesn't! It fails silently. Same for the WIC and XPS executables.

At the moment I don't see how to create an administrative install for use
with Active Directory.

Even if it can be done this way, I presume the client machine will have
individual entries in the Control Panel / Add or Remove Programs list and I
wonder whether other programs trying to detect if .Net 3.0 is installed will
be able to do so.

There really needs to be a proper Administrative install that can do the
whole lot in one go.

Hope you can help.
Thanks
Michael

Hi Michael,

The script at the bottom of that article ignores the WIC and XPS
components of dotnetfx3.exe and the command to extract wcf.exe
does not work. WCF.exe /? indicates there is no /c switch for wcf.exe.

The WIC is not the .NET Framework 3.0's components, it is the Microsoft
Windows Systems Components, the general convention to install the component
is via the Windows Update(Optional). So the NET Framework 3.0 doesn't
contain this component. If you want to install it as command line, you can
download that component package from the following link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=8e011506-6307-445b-
b950-215def45ddd8&DisplayLang=en

Then you need to extract its exe file and run the update.exe (in ite update
subfolder) as the following, this Windows update may need a reboot to take
effective:

update /q /norestart

Please refer to the following MSDN article links for the details about how
to run the update.exe from the command line:

The Package Installer (Formerly Called Update.exe) for Microsoft Windows
Operating Systems and Windows Components
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/deployment/wi
nupdte.mspx


The XPS should be already been integrated in the core components of the
.NET Framework 3.0, it is not provided as a separated component in .NET
Framework 3.0's redist package.


For the issue about the command to extract wcf.exe, I am afraid that .NET
Framework 3.0 Administrator Deployment Guide makes a mistake here. The
corresponding component installation package for the WCF is indigo.exe
(Indigo is the codename of the WCF), there is no wcf.exe is the .NET FX
3.0's package, you just need to replace the wcf.exe with the indigo.exe in
the corresponding line of the script. We are sorry for the inconvenience
which that mistake brought to you.

By the way, the sample script in that Deployment Guide article would
install all the NET Framework 3.0 components administratively, except for
the bug of that non-existed wcf.exe.


Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Hi Gary

from your direct email ... see response below:-

The link you have used above for the redistributable package is for the Beta
2 release which is pre Jan 2006 - nearly a year old!

I'm using the RTM redistributable, File Version 3.0.4506.30 from the MSDN
subscriber downloads.

Over to you...

Michael

 

[Gary Chang[MSFT]]

Hi Michael,

Thanks for the response.

Now the problem is that documentation is out of date as well as its
corresponding .NET Framework 3.0 redist package.

Currently we are contacting the product team on this issue, we will update
you as soon as possible.

Have a good thanksgiving day!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Tommy Campbell - [MSFT]*]

Hi Michael,

The content team is working to update and upload the changes to document
referenced.

Thanks for your patience while this work is being completed.

I will post back as soon as it is ready with a link.

Thank you for pointing out this outdated document!!

Best Regards,

Tommy Campbell, MCSA, MCSE
Microsoft Online Support Engineer
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Tommy Campbell - [MSFT]*]

Hi Michael,

Thanks for your patience over the holiday break. I wanted to let you know
that I am still working on this change request and will update you as soon
as possible.

Happy New Year!

Tommy Campbell, MCSA, MCSE
Microsoft Online Support Engineer
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Tommy Campbell - [MSFT]*]

Hi Michael,

I am posting back to let you know that the documents have been updated to
properly reflect the scripts you noted in error. Please have a look to
confirm this is the case.

Deploying Microsoft .NET Framework Version 3.0
http://msdn2.microsoft.com/en-us/library/aa480173.aspx
Microsoft .NET Framework 3.0 Deployment Readme
http://msdn2.microsoft.com/en-us/library/aa480217.aspx

Thanks very much for your patience while our technical writers worked with
the development team to update these docs.

Best Regards,

Tommy Campbell, MCSA, MCSE
Microsoft Online Support Engineer
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Hi Tommy

The 'Microsoft .NET Framework 3.0 Deployment Readme'
(http://msdn2.microsoft.com/en-us/library/aa480217.aspx) still points to the
Beta-Download and the script still refers to 'Indigo' instead off 'wcf'

Dieter