Difference: InstallationOfWinAppxD (2 vs. 3)

Revision 32016-04-06 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXPresentationServerWinAppxD"

Installation of WinAppxD

Changed:
<
<


________________________________________________________________________
>
>
WinAppxD was replaced by the APPX Login Manager in Release 5.0.0. See this page for installing & configuring the Login Manager.

____________________________________________________________________

 

1) Installation of WinAppxD

1.1) What kind of machines and network do I need for server and clients?

Line: 13 to 17
 
a. Windows NT Server. Note that APPX Presentation Server cannot
be installed on a machine running Novell Netware instead of NT.
You must have a Windows NT machine on which to install APPX
Presentation Server, even if your network still uses Netware
for file and printer sharing. (For your own personal
development purposes, it is possible to install on Windows NT
Workstation, but this is not recommended for production, multi-
user installations)

b. The Windows NT Server Resource Kit. This contains SRVANY.EXE,
required for installing WinAppxD (it also contains many other
useful commands that will make an admin's life easier). You
can buy it separately for about $150 or find it on your
network help desk support technician's "Microsoft Technet" CD.

c. The TCP/IP network protocol. APPX Presentation Server
requires TCP/IP to communicate with clients.

1.3) What software do I need on the clients in addition to APPX?

Changed:
<
<

a. Windows NT, Windows 95 or Windows for Workgroups 3.11.

b. The TCP/IP network protocol. The APPX client uses TCP/IP
to communicate with APPX Presentation Server.

c. If the client is a Windows 95 machine, and you EVER anticipate
sharing the network drive containing the APPX application data
files and running appx.exe (not appx -c) at the client with
APPXPATH set to that network drive, you MUST install the
Windows 95 network file redirector fix provided by Microsoft at

http://support.microsoft.com/support/kb/articles/q148/3/67.asp

to avoid the potential for APPX data file corruption due to a
bug in Windows 95. If you don't do this now, you may forget
to do it later, corrupt your data files, and spend hours on
problem resolution and recovery. You would not be the first
person it's happened to. You have been warned.

NOTE ABOUT URLs: Microsoft periodically rearranges its web
site, so the above URL may or may not be valid. If you can't
find it, use the "Search" option on the MS web site, instructing
it to look in whatever choice includes the "Knowledge Base".
Specify "Qnnnnnn" as what to look for, where nnnnnn is the number
between the "q" and the ".asp". For example, in the above, it
would be Q148367. That should enable you to locate the article.
>
>

a. Windows NT, Windows 95 or Windows for Workgroups 3.11.

b. The TCP/IP network protocol. The APPX client uses TCP/IP
to communicate with APPX Presentation Server.

c. If the client is a Windows 95 machine, and you EVER anticipate
sharing the network drive containing the APPX application data
files and running appx.exe (not appx -c) at the client with
APPXPATH set to that network drive, you MUST install the
Windows 95 network file redirector fix provided by Microsoft at

http://support.microsoft.com/support/kb/articles/q148/3/67.asp

to avoid the potential for APPX data file corruption due to a
bug in Windows 95. If you don't do this now, you may forget
to do it later, corrupt your data files, and spend hours on
problem resolution and recovery. You would not be the first
person it's happened to. You have been warned.

NOTE ABOUT URLs: Microsoft periodically rearranges its web
site, so the above URL may or may not be valid. If you can't
find it, use the "Search" option on the MS web site, instructing
it to look in whatever choice includes the "Knowledge Base".
Specify "Qnnnnnn" as what to look for, where nnnnnn is the number
between the "q" and the ".asp". For example, in the above, it
would be Q148367. That should enable you to locate the article.
 

1.4) Where are the instructions for installing WinAppxD?


You can find them here.

1.5) Where at Microsoft are the instructions for that NT registry patch we need?

Changed:
<
<

As documented in the installation instructions, see the following
URL for instructions on the registry modification to avoid
USER32.DLL initialization errors:

http://support.microsoft.com/support/kb/articles/q142/6/76.asp

NOTE ABOUT URL's: Microsoft periodically rearranges its web
site, so the above URL may or may not be valid. If you can't
find it, use the "Search" option on the MS web site, instructing
it to look in whatever choice includes the "Knowledge Base".
Specify "Qnnnnnn" as what to look for, where nnnnnn is the number
between the "q" and the ".asp". For example, in the above, it
would be Q148367. That should enable you to locate the article.
>
>

As documented in the installation instructions, see the following
URL for instructions on the registry modification to avoid
USER32.DLL initialization errors:

http://support.microsoft.com/support/kb/articles/q142/6/76.asp

NOTE ABOUT URL's: Microsoft periodically rearranges its web
site, so the above URL may or may not be valid. If you can't
find it, use the "Search" option on the MS web site, instructing
it to look in whatever choice includes the "Knowledge Base".
Specify "Qnnnnnn" as what to look for, where nnnnnn is the number
between the "q" and the ".asp". For example, in the above, it
would be Q148367. That should enable you to locate the article.
 

1.6) What special rights must be assigned to the account used to run the WinAppxD process?


As documented in the installation instructions, the account used
to run the WinAppxD process should be in that machine's
Administrators group, and it should have the following rights
assigned to it:

- Act as part of the Operating System
- Replace a process-level token
- Increase quota
- Logon as a service (if it's not already set)

If you do not see these rights in the listbox in User Manager,
click "Show Advanced Rights" and they should appear, so that you
can assign them.

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback