Everytime I want to do something, I would make it a powershell script and save it.
With remote powershell enabled on all workstations, it should be fairly effortless to maintain.
Some individual tasks might take more time than it seems worth at first to figure out how to script it, but int he long run it will be the best solution.
So you're saying I should keep the workstations as they are, but administer them as a group by using remote powershell?
Yes. For example, somewhere on here, I have a Poweshell script posted that let's you install printers.
if you have an ovirt-engine somewhere central, that can reach to all the other locations, you can create a datacentre per location and place standalone hosts in there, using local storage.
Long file names can be a serious pain... for copy and backup reasons.
I recall a NTG client that used a long name for the directories,.. and it made updating nearly impossible Should follow the KISS method... Directory names don't need to be 120 characters long,.. and four deep.
Too bad it is KVM only right now. Not that KVM is bad, it's just early. The have LXC coming "soon" and that will be really awesome. I want VDI on LXC so that we can do it faster and on top of Scale HC3.
i wanted an easier way to copy files to multiple folders and have the folder hierarchy duplicated within parent folders, in other words I wanted to see more stuff in more places all at once.
Q-Dir works pretty well and it seems to work accurately with Onedrive which is a bonus, not all of them do, actually Q-Dir is the only one I've found that can display Onedrive statuses or statii for files and folders.
I like to know if any other alternatives have the Onedrive status functionality.
When troubleshooting on the network, always start at the bottom and work up.
Start with a ping to the IP (not the hostname.)
Then ping the hostname.
Then nslookup the hostname.
These basic steps tell you what is working and what isn't. Don't hop around, use progressive testing and you'll get to answers really quickly.
That's good advice,
We usually start with Aloha based issues such as the control service running on Server, any files telling it to stop, that sort of thing.
Then we move to Windows/networking.
If you know other things are working, you can move up the "stack" to where you can guarantee success. Like if you are transferring files, you know ping works.
You can rename the files obviously, but you can't import them if you change the name it seems.
actually...maybe I cant import because it's already listed.
1f8de455-3499-4cd5-8f71-ac55ced0ada7-image.png
Copy it and change the name, then reload Remmina. You'll now see a copy of the same thing. Go back and delete the original in the file system and reload Remmina again. Original disappears.
Tells me that one should be able to simply dump the connection configs on the minions, tighten down the permission to read only for the user and let them operate.
Its actually Upload default server core, when the terminal has gotten stuck for me, I have cleared the core and then upload the default server core to get it to work again properly without rebooting the machine.
Clearing the core gets only General, Events and Console tabs and loading the default loads all the rest.
@G-I-Jones I like Windows 7 a lot, but since the things are moving forward we all will use something new instead very soon. Just remember how people wanted to stay on Windows XP, but finally updated their OS. The same will happen with Windows 7 and most of users will move on Windows 10 or will choose another option 😉
I usually just copy/paste a Chocolatey install command that does it all at once. Everything else is on separate media that requires no install. Example, copy over games, import them in... such as into Steam.
I was going to mention... with Chocolatey tool choco list -lo just pipe it to a text file.
But that only gives you things installed through Chocolatey. Dustin's OP gives you everything installed through the normal Windows installer process (and registers the install).
I recall when chocolatey didn't use the windows installer process for everything - things are much better now.
It is package by package. Lots of things, through Chocolatey or not, don't use the Windows installer process.
I've not seen Chocolatey not register software installs in Windows, ever.
I have. Many times. Most of the time I think that it does, but it is not Chocolatey that does it when it does.
With what software specifically?
Try installing Sysinternal tools, it will not register at all, that is one example. You can do so with Chocolatey.
I never installed that stuff anyways. That Chocolatey doesn't is nothing new.
I thought you wanted to know which applications would do that, but I guess I read wrong.
@Dashrender Got it. Our departments have their own budget so if they want to print color they can but they figured out fast to be responsible for their own paper.
That seems like a bad approach, since any given department could be forced to stop work "because they overran their paper budget".
Usually, they use the code and pin to know where they are using color but otherwise default is to allow b&w to print without a code.
How does the printer know the difference? Black is a color. .
Really?
Yes really, how does a printer know the difference between CMYK and a page which is black and white.
It's an honest question as I don't know how a Pin to "print in color" would affect this the way you described it.
Also to whoever downvoted, not sure why.
Okay, there are different types of print black and white, gray scale and color which uses CMYK , usually on MFP devices they have different toners for esch of those colors plus black. When a job is sent to the printer with the color setting on the driver it then uses those toners while black and white only requests the black toner
None of the explains what I've asked. How does entering a pin, allow someone to print in color? I've always seen Pin or No Pin for all printing.
Nothing I've ever used has offered "pin for color prints only" etc.
This only occurs, that I've seen, during OOBE when you set up the PC as a local, non-domain, non-Microsoft-Account, user.
Correct, as a standard local account. The "normal" way. Most people don't use AD, even in business this is dropping off quickly. And lots of people don't want to deal with those ridiculous MS accounts that they try to ram down everyone's throats. And who knows how secure those are, anyway.
That is not the normal way to set up windows anymore and has not been for quite a while. The normal way to set up windows is with a Microsoft account. In fact you have to click no to setting up a Microsoft account multiple times in order to set up a PC without a Microsoft account
That's what they promote, but I wonder how many people are actually doing that.
Probably most that don’t use AD. Of course some will not, but not many.
I tend to agree - most home users will use a MS account simply because it's what's presented. IT folks and some programmers might not, but I'm willing to bet it's way over half that do.
Have you seen a lot of home users doing this? I have not, of course my cross section is tiny. But of the ones I see that have zero tech skills, they all skip it because it is scary and confusing.
The option to skip it's obvious enough for most people I run into - they just do it, even if that means setting up a new account.
It is obvious? not really. And even if they see it and click on it, you have to refuse once or twice more.
Whoops - I meant - NOT super obvious... normal users will be guilted into using an MS account in most cases.
yeah the first two times it took me a moment to notice you could skip.
