Here's how to get multiple users on the same machine:
Disclaimer - this process worked for me, but you should make backups, wear suspenders, put on a belt, because you're messing with files... worst case you lose local rowpro data, but it should all be uploaded each row session to their website anyway, so shouldn't be a huge problem to just let it make a new setup if this goes "udder-up"... that's still PC, right?
1- I started with a fresh install of the version above, added my two license keys via "Tools/activate". Downloaded my training plan, and exited.
2 - Copy the "C:\ProgramData\RowPro" folder from source to each users %userprofile%"\Documents\RowPro" folder. (if you need this explained, maybe walk away now? Idonno, you decide.)
3 - Find a drive letter that's open for all users of the machine, I chose "V" for this example, substitute with whatever you want to use for the remainder of these instructions.
4 - Copy the below code into notepad and save as a batch file in each users "%appdata%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup" folder (if you want automatic setup each login.) If not, drop the batch file wherever you want to access it from manually. I like the clean and simple. Call it whatever you want, I used "RowPro symlink mapping.bat"
Code: Select all
@echo off rem drop into %appdata%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup subst v: %userprofile% rem this done once on the PC as an administrator in a command prompt "mklink /d c:\ProgramData\RowPro v:\Documents\RowPro" start "" "v:\Documents\message.vbs"
Code: Select all
CreateObject("WScript.Shell").PopUp "RowPro Ready, now SWEAT.", 5
7 - open a command prompt as administrator (search for cmd if you don't know where it is, right click, run as administrator) and run the below command. This is persistant across all users, so you only need to run this command once. It drops a "shortcut" called RowPro in ProgramData redirecting from ProgramData to the current users Documents directory.
Code: Select all
mklink /d c:\ProgramData\RowPro v:\Documents\RowPro
By copying "C:\ProgramData\RowPro" to each user's Documents directory, you're seeding each user with the same setup as a starting point. Meaning you won't have to activate licenses for each userID, just the once before you started this joy ride. Once they change the Windows user and then RowPro user to their own, download their own training plan, it'll "stick" and not be over written as the next person's "V" drive letter is mapped to their own user ID. You can now share the machine, but keep your own local row data locally.... the way it should have been done to begin with. It can also be mapped to "%appdata%\Roaming\RowPro" if you don't want users to see the RowPro folder or script file in their documents directory. Just an option to 'hide' the stuff the users don't need to see cluttering up their space if that's important to you. If you do that, make sure to adjust instructions accordingly or you'll be surpised by the results.
Oh no, what have I done? Dumbest idea ever!
Not happy? Undo it like this:
Rename the "wormhole" link - "C:\ProgramData\RowPro" to "C:\ProgramData\RowPro-Link"
Copy the first V:\RowPro directory created back to C:\ProgramData\RowPro and you'll preserve that users current data (the other users will lose their local data, sorry) or if you want to go back to before this ride started, just rename "C:\ProgramData\RowPro-original" back to "C:\ProgramData\RowPro".
delete the "%appdata%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\RowPro symlink mapping.bat" (or whatever you called it)
delete the "v:\Documents\message.vbs" file
reboot, log back in and if it works as expected you won't see a drive "V" anymore in file explorer, row pro should work as before and hopefully someone's data is preserved. If that's true you can delete the "C:\ProgramData\RowPro-Link" folder and the various "%userprofile%\Documents\RowPro" folders you copied the original data to.
delete the "C:\ProgramData\RowPro-original" folder if it still exists.
Or just restore from a backup or image you did before you started... you did do a backup as suggested yes?