|
Home > Archive > PostgreSQL Discussion > April 2006 > Why postgres install requires physical access to server in windows
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Why postgres install requires physical access to server in windows
|
|
| Andrus 2006-04-04, 8:26 pm |
| Remote install of Postgres 8.1.3 using Windows installer binary package is
not working (says that console mode is required) even when RDP client is
started with
mstsc /console
switch.
However, using installer package, creating cluster and server process
manually works OK from RDP client!
Any idea why Postgres installer requires physical access to server to
install Postgres ?
Andrus.
| |
| Magnus Hagander 2006-04-04, 8:26 pm |
| > Remote install of Postgres 8.1.3 using Windows installer
> binary package is not working (says that console mode is
> required) even when RDP client is started with
>
> mstsc /console
>
> switch.
It should work fine with this switch. I've used it many times.
> However, using installer package, creating cluster and server
> process manually works OK from RDP client!
>
> Any idea why Postgres installer requires physical access to
> server to install Postgres ?
The problem is in the interaction with the RunAs service. This is being
looked into for the next release.
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
| |
| Andrus 2006-04-05, 9:30 am |
| >> mstsc / console
>
> It should work fine with this switch. I've used it many times.
I ran "mstsc /console" from my XP Proffessional and tried to install
Postgres 8.1.3 in two different
servers:
Windows 2003
Windows 2000
Both cause the following message:
---------------------------
Internal error
---------------------------
The PostgreSQL installer must be run on the system console, not in a
terminal services session.
---------------------------
OK
---------------------------
What I'm doint wrong ?
Andrus.
| |
| Magnus Hagander 2006-04-05, 9:30 am |
| > >> mstsc / console
>
> I ran "mstsc /console" from my XP Proffessional and tried to
> install Postgres 8.1.3 in two different
> servers:
>
> Windows 2003
> Windows 2000
>
> Both cause the following message:
>
> ---------------------------
> Internal error
> ---------------------------
> The PostgreSQL installer must be run on the system console,
> not in a terminal services session.
> ---------------------------
> OK
> ---------------------------
>
> What I'm doint wrong ?
Well, first of all, mstsc/console is not supported on Windows 2000.
Second, make sure that you have the correct version of mstsc. mstsc /?
will tell you if your current client supports the /console parameter.
(If it doesn't, it'll silently eat it and ignore it)
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Andrus 2006-04-05, 11:31 am |
| > Second, make sure that you have the correct version of mstsc. mstsc /?
> will tell you if your current client supports the /console parameter.
> (If it doesn't, it'll silently eat it and ignore it)
I think I use mstsc from XP SP2
mstsc /? returns
---------------------------
Usage
---------------------------
Remote Desktop Connection
MSTSC [<Connection File>] [/v:<server[:port]>] [/console]
[/f[ullscreen]]
[/w:<width> /h:<height>] | /Edit"ConnectionFile" | /Migrate | /?
<Connection File> -- specifies the name of an .rdp file for the
connection.
/v:<server[:port]> -- specifies the terminal server to which you want
to connect.
/console -- connects to the console session of a server.
/f -- Starts the client in full-screen mode.
/w:<width> -- specifies the width of the Remote Desktop screen.
/h:<height> -- Specifies the height of the Remote Desktop screen.
/edit -- Opens the specified .rdp file for editing.
/migrate -- migrates legacy connection files that were created with
Client Connection Manager to new .rdp connection files.
/? -- generates this Usage message.
---------------------------
OK
---------------------------
So /console switch seems to be supported.
However, in Windows 2003 server Postgres installer still says that I must
run in console session.
Any idea why ?
Andrus.
|
|
|
|
|