What Are You Doing Right Now
-
@MattSpeller said in What Are You Doing Right Now:
@DustinB3403 Bears climb trees really well so best not to think about it and just go for the gusto
@MattSpeller as the resident Canadian has near daily encounters with bears.
-
-
@coliver said in What Are You Doing Right Now:
@MattSpeller said in What Are You Doing Right Now:
@DustinB3403 Bears climb trees really well so best not to think about it and just go for the gusto
@MattSpeller as the resident Canadian has near daily encounters with bars.
FTFY
-
@Kelly said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@MattSpeller said in What Are You Doing Right Now:
@DustinB3403 Bears climb trees really well so best not to think about it and just go for the gusto
@MattSpeller as the resident Canadian has near daily encounters with bars.
FTFY
Bears at bars? I think that's something else entirely.
-
-
-
@JaredBusch said in What Are You Doing Right Now:
Reason 12689376 to hate Symantec.
Update to the network definitions last night causes users computer to BSOD when launching one of our applications.
Why are you letting them run SEP to start with?
-
-
-
I imagine in the Linux world backing up and restoring scheduled tasks would look something like this:
- Make a copy of the files related to cron (like crontab)
- [something happenes to your scheduled tasks]
- Replace damaged files related to cron with your copies.
Am I right? Is it truly that simple?
At least with Windows Server, I've found that copying the contents of c:\windows\system32\tasks then transplanting the contents into the same folder for a test server, doesn't cut it. As I'll need to go through an import setp to get stuff setup in the Task Scheduler.
-
@EddieJennings said in What Are You Doing Right Now:
I imagine in the Linux world backing up and restoring scheduled tasks would look something like this:
- Make a copy of the files related to cron (like crontab)
- [something happenes to your scheduled tasks]
- Replace damaged files related to cron with your copies.
Am I right? Is it truly that simple?
At least with Windows Server, I've found that copying the contents of c:\windows\system32\tasks then transplanting the contents into the same folder for a test server, doesn't cut it. As I'll need to go through an import setp to get stuff setup in the Task Scheduler.
Yes, it's really that simple.
-
@travisdh1 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
I imagine in the Linux world backing up and restoring scheduled tasks would look something like this:
- Make a copy of the files related to cron (like crontab)
- [something happenes to your scheduled tasks]
- Replace damaged files related to cron with your copies.
Am I right? Is it truly that simple?
At least with Windows Server, I've found that copying the contents of c:\windows\system32\tasks then transplanting the contents into the same folder for a test server, doesn't cut it. As I'll need to go through an import setp to get stuff setup in the Task Scheduler.
Yes, it's really that simple.
/sigh
I laugh a bit about how I'd have far less head-against-the-wall beatings if we were a Linux shop. -
@EddieJennings said in What Are You Doing Right Now:
I imagine in the Linux world backing up and restoring scheduled tasks would look something like this:
- Make a copy of the files related to cron (like crontab)
- [something happenes to your scheduled tasks]
- Replace damaged files related to cron with your copies.
Am I right? Is it truly that simple?
At least with Windows Server, I've found that copying the contents of c:\windows\system32\tasks then transplanting the contents into the same folder for a test server, doesn't cut it. As I'll need to go through an import setp to get stuff setup in the Task Scheduler.
Depends on the type of file, but generally yes.
-
Breakfast
-
@scottalanmiller It's 1 PM!
-
@EddieJennings said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@EddieJennings said in What Are You Doing Right Now:
I imagine in the Linux world backing up and restoring scheduled tasks would look something like this:
- Make a copy of the files related to cron (like crontab)
- [something happenes to your scheduled tasks]
- Replace damaged files related to cron with your copies.
Am I right? Is it truly that simple?
At least with Windows Server, I've found that copying the contents of c:\windows\system32\tasks then transplanting the contents into the same folder for a test server, doesn't cut it. As I'll need to go through an import setp to get stuff setup in the Task Scheduler.
Yes, it's really that simple.
/sigh
I laugh a bit about how I'd have far less head-against-the-wall beatings if we were a Linux shop.Well of course. Windows is anything but simple (in comparison to other products in their space.)
-
@EddieJennings said in What Are You Doing Right Now:
I imagine in the Linux world backing up and restoring scheduled tasks would look something like this:
- Make a copy of the files related to cron (like crontab)
- [something happenes to your scheduled tasks]
- Replace damaged files related to cron with your copies.
Am I right? Is it truly that simple?
At least with Windows Server, I've found that copying the contents of c:\windows\system32\tasks then transplanting the contents into the same folder for a test server, doesn't cut it. As I'll need to go through an import setp to get stuff setup in the Task Scheduler.
That's even complex compared to our way using Salt
-
@Texkonc said in What Are You Doing Right Now:
@JaredBusch said in What Are You Doing Right Now:
Reason 12689376 to hate Symantec.
Update to the network definitions last night causes users computer to BSOD when launching one of our applications.
Why are you letting them run SEP to start with?
Not my network. This client, we only write custom billing software for.
-
@JaredBusch said in What Are You Doing Right Now:
@Texkonc said in What Are You Doing Right Now:
@JaredBusch said in What Are You Doing Right Now:
Reason 12689376 to hate Symantec.
Update to the network definitions last night causes users computer to BSOD when launching one of our applications.
Why are you letting them run SEP to start with?
Not my network. This client, we only write custom billing software for.
not his circus.
-
Windows 2016 updates.
