[THIN] Re: PS 4.5 on Win2k3 SP2

  • From: "Berny Stapleton" <berny@xxxxxxxxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Thu, 14 Feb 2008 15:29:34 +0000

Yep, I am fully aware of that, but at the same time, the whole idea I
thought of the AMC was to have all the configuration (PS and WI /
NFuse) in the same location. So that the CMC dissapears over releases
as they add more and more functionality to it.

This should therefore mean that OK, I don't have a centralised config
for WI, but if I run the AMC from the WI server, I should still be
able to see the local files of WI and the PS environment (One single
console), why should I have to go to two locations to manage things?

We might as well go back to having the CMC for managing the farm and
the web site for managing WI / Nfuse, it's still two locations.

At the moment, when trying to talk to the presentation servers from
the WI I am getting "Citrix MFCOM service did not respond as expected"
this functionality I thought should have worked out of the box, sort
of like a WI talking to the Citrix XML services in XP and PS.

Or am I missing the point?

Berny

On 14/02/2008, Carl Stalhood <cstalhood@xxxxxxxxx> wrote:
> The AMC can host multiple plugins. There is a PS plugin and a WI plugin.
>
> The PS plugin is used to manage the PS farm. That is the plugin you use to
> view plubished apps, see who is logged in to the farm, etc.
>
> The WI plugin is used to manage the WI sites.
>
> One feature of WI sites is that the WI config file can be stored either
> locally or in a PS farm. Confimgr is only used if you are trying to store
> the WI config file in the PS farm.
>
> My recommendation is to not do that. Instead, when creating the WI site,
> choose the option to use a local file. Then you won't have to worry about
> connecting to PS from your WI servers.
>
> When you run the AMC on the WI server, the WI plugin might ask you to
> communicate with a PS server to find the WI sites configuration files. If
> you are using local files then there is no reason to connect to the
> Configuration Service running on the PS. Instead, choose the option to not
> contact the configuration service. That is how you tell the WI plugin in the
> AMC to not talk to PS.
>
> Note, there are two reasons why a WI server might need to talk to PS (other
> than the normal app browsing and user authentication communication):
>
> The WI plugin for AMC talks to PS to discover and manage centrally
> configured sites. This communication is for management only and has nothing
> to do with how WI operates.
> WI might be configured to store the configuration files in the PS farm. If
> so, IIS will periodically communicate with PS to read the config file. This
> is completely independent of the AMC WI plugin.
> To show how this could be confusing:
>
> If your WI site is configured for local file, the admin might be configuring
> AMC to discover the config service running on a PS farm. Since the WI site
> is using local files, using the AMC to discover the config service on the PS
> farm is not necessary.
> If your WI site is configured for central config (store the
> webinterface.conf file in the data store), the admin might be configuring
> the AMC to not discover the config service. If the AMC does not communicate
> with the PS farm then the admin will be unable to administer the WI Sites.
> Just keep in mind that WI communicating with the PS Farm, and AMC
> communicating with the PS Farm are separate communications.
>
> I can't wait until Citrix gets rid of the discovery wizard in the AMC and
> all of this confusion goes away.
>
>
> Thu, Feb 14, 2008 at 5:13 AM, Berny Stapleton <berny@xxxxxxxxxxxxxxxxx>
> wrote:
>
> > This is exactly it, I can't get this thing to discover remotely.
> >
> > I have a SQL server, two PSs (Seperate farm) and a seperate WI, the WI
> > is also my CTX licensing server and TS licensing server.
> >
> > If I am on of the Access Console on one of the PSs I can see the farm,
> > but if I am on the WI server, and try to connect to the PSs I fail
> > dismally.
> >
> > I have added local machine administrators to the distributed com+
> > users group, and I am obviously an admin on the machine. Given the
> > group policies forced on to this machine, I have had to add
> > ctx_confmgr into the local admins group, this group gives it the logon
> > as service etc rights that it needs. So I am thinking that it might
> > not be a permissions issue, but at the same time, it still could be if
> > I am looking in the wrong place or not thinking of the right thing.
> >
> > I am using local files for WI, I have tried setting up a configuration
> > server before and I thought I was missing something (but wasn't) it
> > seems that nobody here has a good idea on getting it working / working
> > reliably.
> >
> > Is it just me or is all this more than just a little bit crap?
> > (Especially given how long this product has been around for)
> >
> > Berny
> >
> >
> >
> >
> >
> > On 14/02/2008, Joe Shonk <joe.shonk@xxxxxxxxx> wrote:
> > > Works great..  If you trying to access WI and PNAgent, you need to
> install
> > > and run the AMC from your WI/PNAgent server.  You cannot connect to a
> remote
> > > machine.
> > >
> > > Joe
> > >
> > >
> > > On Feb 13, 2008 9:31 AM, Berny Stapleton <berny@xxxxxxxxxxxxxxxxx>
> wrote:
> > >
> > > >
> > > > Has anyone actually got discovery from the access console working?
> > > >
> > > > I have gone through all the normal steps such as turning on network
> > > > com+ etc, but still can't get this thing to go, still hunting, but
> > > > wondering if anyone found a good guide or the mythical "Magic bullet"
> > > > answer to getting the servers talking to the access console (Trying to
> > > > setup web interface and PNAgent stuff) properly.
> > > >
> > > > Berny
> > > > ************************************************
> > > > For Archives, RSS, to Unsubscribe, Subscribe or
> > > > set Digest or Vacation mode use the below link:
> > > > //www.freelists.org/list/thin
> > > > ************************************************
> > > >
> > >
> > >
> > ************************************************
> > For Archives, RSS, to Unsubscribe, Subscribe or
> > set Digest or Vacation mode use the below link:
> > //www.freelists.org/list/thin
> > ************************************************
> >
>
>
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************

Other related posts: