Group Policy Object - Copy Database frontend from NAS WITH icon
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
Just to be sure... are you sure it is the front end that you are copying and not the back end (or both?) Where is the shared DB reside that everything is pointing to?
We put the Back End on a Server Share. This is definitely the Front End.
I'm with scott - I'm surprised it's Access on the backend and not having the same problem... there presumably would be a similar temp file for the backend part, and that would be shared by everyone logged in at the same time... i..e problems.. but, apparently someone figured a way around that.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
MDB is the database (backend).
-
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
MDB is the database (backend).
what other file types does Access use? I'm assuming he has two - the front one, and the back end one.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
Hopefully .accdb, not .mdb. AccDB replaced MDB 13 years ago, lol.
-
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
MDB is the database (backend).
what other file types does Access use? I'm assuming he has two - the front one, and the back end one.
Ah, I see. If you split them, then the back end of the front end is incorrectly referred to as the front end file. It's a back end to the front end. See my note earlier about Access (the front end) needing to be installed.
This is not the front end being copied, it's a local back end used by the front end.
Yes, in that case, it's an AccDB file that needs to be copied, because it is a backend, that MS refers to as a front end file. Ugh.
Much like how Hyper-V's first virtual machine is named the physical. Argh.
-
So yes, in that case, if we are talking about a database file (this is why I pointed out that DB files are back ends) it needs to be copied and can't just be a short cut. If we are talking about a front end (which is an application, not data storage) then it can be a short cut.
-
For clarification, from wikipedia (but all sources agree..)
In software architecture, there may be many layers between the hardware and end user. The front is an abstraction, simplifying the underlying component by providing a user-friendly interface, while the back usually handles business logic and data storage.
MDB and AccDB files are data storage (e.g. back end). Access the application is the front end.
-
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
I'm looking for an option similar to User Configuration>Preferences>Windows Settings>Files where you can copy a file from a directory directly to C:%userprofile%\Desktop, but I want to be able to include a custom made .ico.
....
Any experience or ideas?Now if we have figured out that this is a database file, not a front end application component that is stateless, then the need and reason for copying the files makes sense. It's a stateful backend file called a front end, but that isn't a front end (facepalm)...
Then a script is one option that will be decently easy. Or a tool like Salt or Ansible will do this easily. GPO probably can, I just don't know the mechanism that would normally be used outside of just calling a script.
-
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@Dashrender said in Group Policy Object - Copy Database frontend from NAS WITH icon:
Is your manual process working for 100+ users you have now?
Yea, so we've been using this method for longer than I've been here, so at least 4 years. I was always told "you have to copy the Front End from the NAS to the desktop, if you create a shortcut to it, bad things happen".
I bet - because when you do that - the temp file for the DB is on the NAS - and every person who's using it at the same time is using the same temp file - and that's bad, definitely bad!
See now we're getting it, I don't know where I went wrong at, but this is what I was trying to say the whole time.
So you solve the problem by placing the front end DB file to c:\DB\db.mdb, and create your shortcut to c:\DB\db.mdb with your custom ico file. problem solved.
Hopefully .accdb, not .mdb. AccDB replaced MDB 13 years ago, lol.
It's .accde (Front End), .accdb (Back End)
-
@scottalanmiller said in Group Policy Object - Copy Database frontend from NAS WITH icon:
@G-I-Jones said in Group Policy Object - Copy Database frontend from NAS WITH icon:
I'm looking for an option similar to User Configuration>Preferences>Windows Settings>Files where you can copy a file from a directory directly to C:%userprofile%\Desktop, but I want to be able to include a custom made .ico.
....
Any experience or ideas?Now if we have figured out that this is a database file, not a front end application component that is stateless, then the need and reason for copying the files makes sense. It's a stateful backend file called a front end, but that isn't a front end (facepalm)...
Then a script is one option that will be decently easy. Or a tool like Salt or Ansible will do this easily. GPO probably can, I just don't know the mechanism that would normally be used outside of just calling a script.
Yea, I'm just going to run a script for the xcopy and then configure the GPO to point to it's location as @Dashrender suggested earlier. Makes sense, and seems pretty straightforward and easy.
