@scottalanmiller said in Gaming - What's everyone playing / hosting / looking to play:
Just picked up Ori and the Blind Forest
Super salty this isn't on PS4.
@scottalanmiller said in Gaming - What's everyone playing / hosting / looking to play:
Just picked up Ori and the Blind Forest
Super salty this isn't on PS4.
They meant source code, but whoever wrote it doesn't know what source code is and it makes no sense.
What they should have said is...
Install from TarBall without a Repo
Or CentOS via RPM, Ubuntu via DEB, etc.
Gotcha. Thanks, I'm almost a pro at this already.
@scottalanmiller said in HelpDesk Options:
@G-I-Jones said in HelpDesk Options:
@scottalanmiller said in HelpDesk Options:
@G-I-Jones said in HelpDesk Options:
@scottalanmiller said in HelpDesk Options:
@G-I-Jones said in HelpDesk Options:
Source: All command line?
I don't understand this one. All scripts are source. No matter how you run Zammad, it is source. There is only the source code, that's the entire application.
It was phrased as a question because I didn't understand it.
I'm not sure what the question was, though
What does the option mean on zammad.org?
I was just looking around their site to see if I could figure out what prompted you to ask about that word.
Zammad is using the term 100% wrong here and it is gibberish. What they mean is installing from a tarball (tarball is a specific type of compressed file like a zip file, but common everywhere outside of Windows) versus installing from a repo. Whoever wrote that part of their documentation is completely confused and doesn't know what they are writing.
Zammad is a Ruby on Rails application and as such, is a script, and as such is always source.
Source is short for source code and always means the code of the application, there is no exception. Every install method that they offer (or could offer) is equally source. The one that they call source is no more or less than any other. It's easy to tell how they got confused, it's a non-developer who saw some of these things in a different situation, totally misunderstood what they saw, and repeated it wrong when writing this doc. I could make a video just explaining that, lol.
But it is always source, and the term is completely misused. That's all that you need to know.
Ah, see, I thought "maybe they mean Source Code" but in all honesty that wouldn't have gotten me much further. You're explanation is both needed and appreciated.
@scottalanmiller said in HelpDesk Options:
@G-I-Jones said in HelpDesk Options:
Is source the word for this DOS style command line stuff in Linux?
No. The term for the command line stuff is always "command line interface" or CLI. The thing that takes your commands at the command line is a shell. CMD.exe and PowerShell are the big shells on Windows. BASH is the big shell on Linux. You can also use PowerShell on Linux, works just fine. No reason to, it's a horrible shell, but it is there and totally works - it really shows how slow it is when you use it outside of Windows and have things to compare against.
But the terms in Linux aren't different from Windows. It's all the same stuff. CLI, shell, source, etc.
So I'm reading through the install guide and noticed for the Ubuntu option is says "install on Ubuntu via DEB". Is DEB a shell?
@scottalanmiller said in HelpDesk Options:
@G-I-Jones said in HelpDesk Options:
@scottalanmiller said in HelpDesk Options:
@G-I-Jones said in HelpDesk Options:
Source: All command line?
I don't understand this one. All scripts are source. No matter how you run Zammad, it is source. There is only the source code, that's the entire application.
It was phrased as a question because I didn't understand it.
I'm not sure what the question was, though
What does the option mean on zammad.org? Is source the word for this DOS style command line stuff in Linux? I'm just learning this stuff and don't know any of the terminology.
I would run on either CentOS or Ubuntu.
Thanks. I think that's what I'll be trying.
@scottalanmiller said in HelpDesk Options:
@G-I-Jones said in HelpDesk Options:
Source: All command line?
I don't understand this one. All scripts are source. No matter how you run Zammad, it is source. There is only the source code, that's the entire application.
It was phrased as a question because I didn't understand it.
Okay guys, all my other important shit is done and I have some time to really grind out some learning here. I'm going to try making a VM with one of the options listed on zammad.org for a HelpDesk. This is a prime opportunity to get my feet wet in Linux as it's something we need to get up, but there isn't a terrible rush. Plus, I enjoy coding.
As far as Linux goes, and of the list provided below before I start reading trying to figure out what the hell I'm doing, does anyone have anything helpful to point out about any of the options?
So far I have:
Source: All command line?
CentOS: better at Ubuntu with server stuff, but may lack in end user experience
Debian: tiered releases, lacks the user friendliness of Ubuntu.
Ubuntu: desktops or servers. free and common.
Docker: something about a container that works well inside Ubuntu?
I'm planning on reading more, but I'm just scratching the surface here and don't want to get off on the wrong path here spending hours learning one I won't use. Any tips would be appreciated.
@Obsolesce said in New VM keeps turning off:
Is the OS licensed properly? I thought it shuts down if it's not, not sure if that still happens.
Yea, it's Activated and all that.
Okay, so I guess maybe it was one of the guest updates or something that fixed it. It hasn't happened once yet. Solved?
@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.
@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:
@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.
@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.
@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".
@scottalanmiller - This is an Access Front End and Back End. It's something that is a shared design among many other similar organizations to mine across the United States. Some of which have ditched it for obvious reasons you've outlined. Hopefully we'll get away from it soon.
@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:
but I need a copy of the file and not a shortcut because it's a database front end that many people will have open and are writing to simultaneously.
It's standard to use a shortcut for that. As a front end, it specifically can't be written to and has no need to be local. Once you execute the shortcut, the front end is loaded into RAM and that it's a single starting file has no effect.
lol, I'm clearly not an Access guy.
So what you are saying is that I could have 100+ users, with both x64 and x32 front end versions open for a backend, and everything is going to be just fine. So I should go ahead and just make it a shortcut to the frontend on the NAS.
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.
I typically do this at my organization with shortcuts very easily via User Configuration>Preferences>Windows Settings>Shortcuts, but I need a copy of the file and not a shortcut because it's a database front end that many people will have open and are writing to simultaneously.
Any experience or ideas?
@DustinB3403 said in New VM keeps turning off:
@G-I-Jones said in New VM keeps turning off:
@EddieJennings said in New VM keeps turning off:
You've likely checked for this, but are there events in the Application logs that talk about a bugcheck around the time of the shutdown, or does a
C:\Windows\Memory.dmp
file exist that was created around that time?There were no events about a bugcheck around the time of the shutdown. Something I do find curious though, is the fact there isn't a %SYSTEMROOT%\MEMORY.DMP file at all.
There usually isn't if verbose logging isn't enabled with these types of crashes.
Ah, well it is now, so time will tell I suppose. Thanks again.
@pmoncho said in New VM keeps turning off:
@G-I-Jones said in New VM keeps turning off:
@black3dynamite said in New VM keeps turning off:
UEFI or BIOS VM?
If UEFI, is secure boot enabled?UEFI, Secure Boot is Disabled
You may want to go into (on the guest) System Properties -> Advanced Tab -> Startup and Recovery -> Uncheck "Automatically Restart"
That way if you get BSOD, you can see it on the screen.
Then look for the memory dump like @EddieJennings stated. Then use program @DustinB3403 mentioned to figure out WTH is going on.
If you don't know if it is the whole host, whip up a linux machine real quick and let it run. If the Exchange server halts, see if you can still access the linux machine. Just an option.
Will do, thanks for the tips.
@EddieJennings said in New VM keeps turning off:
You've likely checked for this, but are there events in the Application logs that talk about a bugcheck around the time of the shutdown, or does a
C:\Windows\Memory.dmp
file exist that was created around that time?
There were no events about a bugcheck around the time of the shutdown. Something I do find curious though, is the fact there isn't a %SYSTEMROOT%\MEMORY.DMP file at all.