That was Monday/Tuesday. Here I am again on Wednesday doing the same thing, but with a different client in a different part of the country.
It's Windows Server 2003 which has, in the past, been my nemesis, but I'm not going to let it beat me. Am checking all the usual things: -
- Nothing listening on the port range 100xx ( WebSphere ) and 50000 ( DB2 UDB )
Good thing I checked; Backup Exec Remote Agent for Windows Systems was running on 10000
- Signed on as a local administrator
- Data Execution Prevention (DEP) not getting in the way
Again, I know that caused problems with a Lotus Quickr Services for WebSphere Portal installation in the past
- Using MSTSC /CONSOLE to start the RDP session
This gives one more console-like access than the normal MSTSC interface; I know that's caused problems for others in the past
- Fully qualified hostname
Belt and braces; this is what I've always done, so I'll always do it
- No need for hosts file updates
- "Real" IP address
- Password policy clearly understood
I created a "dummy" account with the same password that I'm going to use for the portal installation just to check that it didn't breach the local/site password rules
- Enough RAM in the server
Only have 1 GB - need 2 GB as a minimum; being fixed as I write ... I now have a different server with 2.5 GB
2 comments:
And it worked - went for lunch and, when we got back, there it was, all nice and shiny and ready to go.
By the end of the day, had a bunch of pages, a customized theme, some WPF/WDF portlets etc. etc.
I have actually tried to follow your "recipe" here... I have previously installed om 2003 server with no problems.. now I have server on a domain.. Even though I create a dummy user like you suggest I still get an error that I am failling to conform to policies.. and PE 6.1.01 will not continue past this point.. Made for a great POC.. NOT. and still working on it..:/
Post a Comment