| | | 
Sepal

Group: Moderators Last Login: Today @ 4:06:35 PM Posts: 1,183, Visits: 9,261 |
| Rather then using WshShell.Run use WshShell.Exec this will hide the cmd window. better yet you can use WshShell.Exec and redirect the out put to a log file, you can reference http://www.microsoft.com/technet/community/columns/scripts/sg1002.mspx to help you accomplish the redirection of output.
Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post. |
| | | | Junior Member
       
Group: Forum Members Last Login: 1/24/2006 12:52:57 PM Posts: 14, Visits: 14 |
| | I'm a little confused. I am trying to setup point client on a terminal server to connect to a PDS server on the local network with the client. this is what I've done: 1. Installed Point client to f:\winpoint (other point folders reside on f: too) 2. copied f:\winpoint to c:\documents and settings\default user\winpoint 3. copied f:\winpoint to d:\winpoint (not sure why this step is done) 4. logon as a user...I am getting an "compilation error expected end of statement" when trying to run the scripts - I copied to notepad and named .vbs and am running manually with cscript. 5. Configured access to PDS through Point Administratior. I tried changing the winpoint.ini file for that particular user (in their documents and settings\windows folder) to following and I get an application error when logging onto PDS. [User Information] User=NTG HOST 1 Company=NorthStar Technology Group, Inc. Serial=234-3016-0000 Serial+=QhDSf6VZmpR0ASyr/58HBA==~@Pnt128~ GUID=0669FF22-1F92-4F31-94AF-1DF700C11321 [Directories] Folder0=f:\PNTDATA Folder1=SENTINEL Application=F:\WINPOINT Templates=F:\PNTTEMPL User=F:\WINPOINT\user [Program Version] ConfigServer=0 Program=Point Version=5.2 Build=744 Source=C:\DOCUME~1\ADMINI~1.FIR\Desktop\Point InterFace_Version=22 [Settings] PLN=1 DATA_FOLDER_MGR=1 PPP=1 ClassName=Afx:00400000:8:00010003:00000000:0002006D [PDS] Enable=1 WebService=https://xxx.xxx.com/service SecurityKey=q4nwpTp5r07xN1gLAz+rTErEPjj24acyghY+rKs20/s=~@Pnt128~ [Point Size Info] Max=1 Top=0 Left=0 Bottom=600 Right=800
Ken |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 10/24/2008 2:09:26 PM Posts: 4, Visits: 48 |
| | I currently have users that I have done an admin installation using netsetup, and am putting a TS in place to service about 10-15 users. Should I do an admin "netsetup" installation or a standard installation on the TS? |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 7/25/2006 2:07:16 PM Posts: 1, Visits: 8 |
| | Hi, I'm trying to implement your solution on a new Win2k3 TS, but I'm confused about a few things: 1) what is the "w" for in the line item "subst w: "%userprofile%\winpoint" 2) what is the "w" for in the line item "Set CrntPoint = filesys.Getfile("w:\winpoint.exe") Maybe I'm being to simple minded about this, even though I've installed several Win2k/2k3 TS boxes in different environments, but Point seems to be the toughest one to tackle. In any case, here's the scenario: Point database resides on a Win2k Member Server. New Win2k3 TS box added to the network to replace previous Win2k TS box. New Win2k3 TS box doesn't want to play as well as the Win2k TS box. Point database (includes PNTTEMPL and PNTDATA as subfolders) is mapped as G:\ on the network. User network (home) directories are mapped via a login.bat file as F:\ The confusion comes from not being sure which drive letters should be changed/substituted in your script to match our environment.
Any help would be most appreciated. Regards, J. Rugel |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 5/30/2006 11:57:50 AM Posts: 2, Visits: 4 |
| | Please help! I am not used to using scripts to do administrative tasks. When I try to copy these scripts to notepad and save as .vbs, I get a compile error when trying to then run them. What is the exact process I need to get these scripts to run? What I have completed so far: change to install mode install point change back to execute mode login as regular user try to run scripts try again as administrator I am getting a expected end of statement error every time. Please help, our entire organization is down until I get this back up and running on a term server. Thanks a bunch, Richard Johnston Sr. Dummy!
Just a point Newbie |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 5/10/2007 1:46:50 PM Posts: 8, Visits: 21 |
| | Here's my script TS login script to setup users. It takes a lot of ideas from the original post, but is a little more simple for those who might be old school. REM ************************************************************************ REM MAP USER DRIVES REM ************************************************************************ if exist "d:\users\%username%\winpoint\" goto mapdrive md "d:\users\%username%\winpoint\" REM ************************************************************************ REM map local user dir to W drive REM ************************************************************************ :mapdrive subst w: /d subst w: "d:\users\%username%\winpoint" REM ************************************************************************ REM check if upgrade is required REM ************************************************************************ if exist W:\06-07-06.TXT GOTO INIFILES set session=%sessionname% msg %session% /TIME:20 /V "Upgrading to latest version of Point. Please wait patiently. Thanks and have a great day!" REM ************************************************************************ REM copy winpoint files over REM ************************************************************************ XCOPY c:\zWINPOINT_BAK "d:\users\%username%\winpoint\" /e /s /y /r REM ************************************************************************ REM CHECK WHICH WINPOINT.INI TO ASSIGN REM ************************************************************************ :INIFILES ifmember.exe /v /l UFG\MultiPointUsers IF ERRORLEVEL 1 GOTO MANAGERS :LONGBEACH xcopy d:\users\ini_files\winpoint.ini "%userprofile%\windows\" /y GOTO END :MANAGERS xcopy d:\users\ini_files\managers\winpoint.ini "%userprofile%\windows\" /y rem update desktop shortcut rem del "%userprofile%\desktop\point.lnk" /q rem xcopy "c:\program files\calyx software\point.lnk" "%userprofile%\desktop" /y :END rem EXIT |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 8/9/2006 2:04:17 PM Posts: 3, Visits: 17 |
| | Hi all, I was wondering if someone can help me clarify Point installation on TS enviroment. I got Point 5.2 installed on 2003 TS server with the following setup and eveyrthing is working fine: (1) Login as administrator and install Point on TS server (Program directory=C:\Winpoint; Winpoint.ini in C:\winnt) (2) Copy C:\winpoint\*.* to each user directory c:\document and settings\userx\winpoint (3) Copy Winpoint.ini to each user directory c:\documents and settings\userx\windows. (4) In Winpoint.ini, Application=C:\DOCUMENTS AND SETTINGS\UserX\WINPOINT User=C:\DOCUMENTS AND SETTINGS\UserX\WINPOINT\user (5) Point Icon on desktop is pointed to "C:\Documents and Settings\UserX\WINPOINT\Start\start.exe" Here are my questions: (1) When I rename the C:\Winpoint directory and login as Userx, using Point in C:\document and settings\Userx\Winpoint\Start, Point does not work any more. Error message "Could not locate Configuration server. Please contact your Network Administrator" I thought the Application= in Winpoint.ini dictates where Point application resides? Why is still looking at C:\Winpoint? instead of C:\documents and settings\Userx\Winpoint\? (2) If the program is still looking at C:\Winpoint, What's the purpose to have entire C:\Winpoint directory copied to each user profile location? (3) What's known issue with Point 5.3 on TS? Thanks!!! |
| | | | Forum Guru
       
Group: Forum Members Last Login: 9/8/2008 5:20:14 PM Posts: 51, Visits: 183 |
| Please see comments below:
I got Point 5.2 installed on 2003 TS server with the following setup and eveyrthing is working fine:
(1) Login as administrator and install Point on TS server (Program directory=C:\Winpoint; Winpoint.ini in C:\winnt)
(2) Copy C:\winpoint\*.* to each user directory c:\document and settings\userx\winpoint
(3) Copy Winpoint.ini to each user directory c:\documents and settings\userx\windows.
(4) In Winpoint.ini,
Application=C:\DOCUMENTS AND SETTINGS\UserX\WINPOINT
User=C:\DOCUMENTS AND SETTINGS\UserX\WINPOINT\user
(5) Point Icon on desktop is pointed to "C:\Documents and Settings\UserX\WINPOINT\Start\start.exe"
ISUPPORT - This should be "C:\Documents and Settings\UserX\WINPOINT\winpoint.exe" Start is for the Automated remote install. I don't use it on TS servers. When I want to upgrade a TS server I do it manually. The user needs to have admin rights to the machine to make auto install work.
Here are my questions:
(1) When I rename the C:\Winpoint directory and login as Userx, using Point in C:\document and settings\Userx\Winpoint\Start, Point does not work any more. Error message "Could not locate Configuration server. Please contact your Network Administrator" I thought the Application= in Winpoint.ini dictates where Point application resides? Why is still looking at C:\Winpoint? instead of C:\documents and settings\Userx\Winpoint\?
ISUPPORT - I find that Point always needs the original installation point. So c:\winpoint has to stay there. The idea of having the zWinpoint directory is so that when a user logs on they can get a fresh copy of the Winpoint directory w/o missing files in use or whatnot.
(2) If the program is still looking at C:\Winpoint, What's the purpose to have entire C:\Winpoint directory copied to each user profile location?
ISUPPORT - The real reason for having C:\winpoint copied to each user's profile is to avoid conflicts with the "work" directory and other settings which seam to pop up with each new version of point. Our initial reason was to avoid print jobs from stepping on each other. If one of our users printed for borrower x, and one for borrower y, occaisonally we'd end up with a printout with 1/2 of x's info and 1/2 of y's info. That has gone away since we gave each user a copy of Winpoint.
(3) What's known issue with Point 5.3 on TS?
ISUPPORT - I haven't seen many issues with 5.3. I've had some issues with TS + Point 5.3 + PDS, but those were specific to our config.
I hope this helps... |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 8/9/2006 2:04:17 PM Posts: 3, Visits: 17 |
| | |
|