Office 2003 SP1 and .NET setup issue

G

GT-MATH MSDNAA

Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 
B

Bob Buckland ?:-\)

Hi Diego,


In step 12 - will 'stop' asking for files from Office Admin
point? Can you clarify?

In steps 9 - 11 the purpose of those steps in that sequence?

=======
Hi,

I have found a problem installing office 2003 from an Administrative
installation point. The way to reproduce it is:

1. Install office 2003 from the cd with setup /a in a machine that i will
call server.
2. Apply all administrative updates starting from SP1 to the office 2003
administrative installation point on the server machine..
3. Make a clean install windows XP SP2 on a client machine.
4. DO NOT apply any windows updates yet. Just plain XP SP2.
5. Install Office 2003 on the client machine from the server using the admin
point install.
6. Create a new user account say "test" and log in as that account.
7. Try to launch any of the office components, e.g. Word.
8. It works fine.
9. Log back in as administrator and delete the profile for the account test.
10. Install .net 1.1 and reboot and then apply the .net 1.1 SP1
11. Log back in as the test user
12. Try to launch word. Now a section of the office setup will come up and
will stop asking for the files from the administrative installation point.

Why is this happening. This is a huge annoyance for unattended installations.

Thanks,

Diego>>
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Outlook Desktop (latest) stopped syncing IMAP accpounts from selfowned Mail server. 0
office 2010 install error. 2
ODBC error 100 when accessing Bookkeeper version 15 software (accounting software using Access dbase) 0
ISO best steps to export (import) all from Outlook 2003 to Outlook in MS 365 0
Office 2003 Administrative Installation Point Question 0
Updates for administrative installation Office 2003 0
Re: Install error, cannot find ProPlus.WW\ProPLSWW.cab 0
Office 2007 installation error. 0

Top