|
| | | Junior Member
 
Group: Forum Members
Last Login: 8/1/2007 10:47:04 AM
Posts: 21, Visits: 42 |
| | I am setting up PDS client on a TS. The reason for this is that we use another program (PushMX) that piggybacks on Point to track the loan process. There is no remote access to this program other than via TS. I've been reading a lot of posts here and am getting confused. The problem is that it is hard to distinguish a difference between proper setup for standard Point installations on a TS and for PDS clients on a TS. 90% of the problems associated with the TS seem to be the "Winpoint.ini" file and the "Work" folder. What should the Winpoint.ini look like when using PDS? Seems to me that using the "User=UserAppDataPath" parameter works. What problems are associated with this? As for the Temporary= portion of the Winpoint.ini, I don't have this even listed. Here is my winpoint.ini file. What should I be changing? My main concern is that the users will all be using the same Work folder. Are my worries justified? Directories]
Folder0=SENTINEL
Application=C:\WINPOINT
Templates=C:\PNTTEMPL
User=UserAppDataPath
Folder1=SENTINEL
[PDS]
Enable=1
WebService=https://xxxxxxxxxxxxxx.com/service
SecurityKey=xxxxxxxxxxxxxxxxxx
[Program Version]
ConfigServer=0
Count=8
Source=\\vit002\D
Program=Point
Version=5.4a
Build=856
[User Information]
User=Network User
Company=Strategic Capital Mortgage
Serial=xxx-xxxx-xxx
Serial+=xxxxxxxxxxxxxxxxxxxx
GUID=478B5B92-16E6-4C9A-8E9E-AFA28F6172F5
[Settings]
PLN=1
DATA_FOLDER_MGR=1
PPP=1
ClassName=Afx:00400000:8:00010003:00000000:001A014D
[Point Size Info]
Max=1
Top=0
Left=0
Bottom=600
Right=800
|
| |
| | | 
Sepal
Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261 |
| If you don't specify temporary then they will use the same work folder. there are issues with non iis severs and viewing credit when using the userapppath variable for temporary in point 5.4. This should be resolved in 6.0 however.
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: 8/1/2007 10:47:04 AM
Posts: 21, Visits: 42 |
| | Thanks for shedding some light on this, BetaFisch. Does installing IIS take care of the problem viewing credit when using the userappath variable for temporary? How long before 6.0 ships? Seems like there aren't nearly as many issues when using Point as a PDS client on a TS as there are using stand alone Point on a TS. Is there anything else that I should be aware of going forward? The natives are getting restless and want a solution that works. |
| |
| | |
Sepal
Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261 |
| | I am not sure about the ramifications of installing iis with TS. Point 6.0 has started to ship so if your current you should receive one in a few weeks. The only other issue that comes to mind is getting email and pdf support working. I think the typical solution is to run these features once logged in as admin.
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: 8/1/2007 10:47:04 AM
Posts: 21, Visits: 42 |
| | For the email and PDF parts, logging in as admin and running through them once sets it up for all users? I'm not sure about IIS on a TS either. I sure wish I had 6.0 here already. |
| |
| | |
Sepal
Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261 |
| I think just one login.
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: 8/1/2007 10:47:04 AM
Posts: 21, Visits: 42 |
| | Forgive my ignorance on the topic of temp files. In the PDS parameters there is an entry for the Temporary Path (see image below). Would this be the PDS equivalent to the temporary= path that is found in the winpoint.ini that stand alone Point uses? If so, then all users are using the same directory for temporary files on the PDS server. Will this not cause the same problems that are found when terminal server users are mapped to the same temporary directory? Also, is this why I don't see an entry in the winpoint.ini file on the TS for a temporary= since it's already defined as a folder on the PDS? What should the NTFS rights be to the temporary folder on the PDS? 
|
| |
| | |
Sepal
Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261 |
| | no this is completely different. you don't see temporary in winpoint.ini because its a hidden value with a default setting. temporary on pds needs to give asp.net and filesync full rights.
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. |
| |
|
|