|
| | | Forum Newbie
Group: Forum Members
Last Login: 9/14/2007 11:32:44 AM
Posts: 2, Visits: 114 |
| | For those that have installed PDS 6.0, are you having any serious problems to speak of. Also since you have to install Point 6.0 on all workstations accessing PDS is there any problems with Point 6.0. Thanks. |
| |
| | | Junior Member
Group: Forum Members
Last Login: 11/1/2007 3:17:08 PM
Posts: 15, Visits: 62 |
| We have been using PDS since version 5.0 and upgrading every year. We just did the upgrade this last weekend from PDS 5.3 to PDS 6.0 along with the client upgrades. We have 7 branch locations, 100 users, and the installs actually went VERY SMOOTH . This was the easiest by far. One thing that we figured out that is NOT in the instructions was how Point clients previously configured via Netsetup can automatically upgrade if you just replace the existing Netsetup folder with the new 6.0 version. I knew we could do small patch installs (from 5.4 to 5.4a for instance) via the Netsetup, but nothing in the instructions stated that you can do an entire client install of Point 6.0 this way without requiring the user to do anything. All we did was make sure the config.ini file had a different "Count=" than the original causing the client machines to recognize something was different and the install ran automatically the next time the user launched the Point client. We did have to temporarily give the users Admin rights to their local computer for the install to run, but other than that it went off without a hitch. Mike Shaw Network Manager Pacific Residential Mortgage, LLC.
Mike Shaw Network Manager Pacific Residential Mortgage, LLC. |
| |
| | | 
Sepal
Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261 |
| Sorry that should be in the instruction sorry. All you should need is do the network admin install on the same machine, it will pick up the old settings update the contents of the netsetup folder and the config.ini. The trick is getting the users to have admin 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.  |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 9/5/2007 12:50:39 PM
Posts: 9, Visits: 10 |
| I had an issue upgrading on Win2003 SBS 64-bit edition where it wouldn't update the permissions, but I changed what little needed changed using the matrix. It also seems that Filesync wasn't starting correctly on reboots, so I wrote a batch file to run on startup:
sleep 30
net stop CalyxPDSFileSync (or whatever it's called, I'm not at the machine now)
sleep 30
net start CalyxPDSFileSync (again, not sure on the name)
For "sleep" to work, you need to download the 2003 resource toolkit.
Also, unresolved is an issue where users can't MOVE a file from Prospect to Borrower. They click the Move button, select the proper options, and the file still shows up under Prospect and NOT under Borrower.
|
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 9/5/2007 12:50:39 PM
Posts: 9, Visits: 10 |
| Was informed that support for Win2k3 SBS x64 is dropped, so last night from 10pm-4am, I downgraded to Win2k, re set up all my shares, reinstalled my antivirus LAN update server, and reimported PDS data.
Currently, when users open a file, and exit, it stays reserved until it times out. This seems totally wrong. Plus, when they save it, the changes do not appear, and reentering the file, it's read-only. I read another post that said that it could be that the server is running high cpu (possible) or low ram (I've got 2GB), and the file is just still in the temporary folder. However, there are only MAYBE 10 active users at a time, so this doesn't seem right.
Also, in previous versions, if you couldn't access or log in to the server, it would drop you into Point with access only to your local data folder. Now, Point exits out, and to access your local data folder, you have to disable server access by going into Point Admin. If this is intentional, could we at least get a dialog box that ASKS if we want to run Point with just our local data folder? Or on the window with username/pass, there could be a "Local Data Only" button.
That would be great. |
| |
| | |
Sepal
Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261 |
| | Filesync service is not running. regarding the new point behavior. This is a new feature of Point/PDS for local datafolder control, so the user does not have permision to use their local folders.
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. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 9/5/2007 12:50:39 PM
Posts: 9, Visits: 10 |
| BetaFisch (8/24/2007)
regarding the new point behavior. This is a new feature of Point/PDS for local datafolder control, so the user does not have permision to use their local folders.
--------------------
You should be a little more verbose and maybe link to a support document like:
http://pdskb.calyxsoftware.com/article.aspx?id=11747
because you didn't explain that I as PDS administrator could control whether or not people had Local Folder Access, you merely stated that the lack of permission was a new feature in PDS. I was writing you a sarcastic comment about how removal of a feature doesn't constitute a feature, IMFO, when I found the article myself.
However, you still did not address the secondary problem:
When a user is denied server access due to a)internet issues, b)server issues, c)user error, they CANNOT ACCESS THEIR LOCAL DATA FOLDERS. That is something I don't have control over. Why can a user not choose to not access PDS? What if I don't want to log in to PDS, but I want to access my local files? What if I forget my password, and need to work with my files? I know I can click File > Open File, then navigate there every freaking time, but I don't think that's super-feasable.
Again, here's a feature request (do you have a bug-tracker or feature-request system, because that would be great.):
1. On login dialog, give option to access local files RATHER THAN LOG IN. Please. So the user doesn't need to learn to use Point Administrator if the server is down or inaccessible.
It's completely reasonable, and can't hurt anybody. It's software running on the client machine, and they can't opt out of connecting to a server that's configured, and that's just stupid. |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901 |
| | In the PDS Admin site there is a setting to enable/disable local data folder access for users or groups. Local Point Control
With this version of PDS, you can also decide if users are allowed to access local, non-PDS data folders. By adding or removing users from Local Data Folder Access, you can have complete control over the borrower and prospect files in your organization. During installation, you can choose to allow or deny users access globally. By default, users will NOT have access to local data folders
Bryan
Point Product Manager |
| |
| | |
Sepal
Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261 |
| You see this because its the first time your users are on 6.0 and they can't connect to the server. Therefore Point does not know if they have access to local data folders or not. Point chooses the secure option and denies them. This behavior will be different once they connect to the PDS server and receive local data folder access permission. From that point forward if they cannot connect to PDS they can access the local Data Folder.
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. |
| |
| | |
|