I ran sfc from an administrator command line like this:
/scannow /offbootdir=d:\ /offbootwindir=D:\Windows
24 hours on, it's still running with the cursor just flashing on the next line. Can I start another process to inform me of progress? If so, how?
The "helpful wizard" that runs upon booting a new Windows 10 laptop, (once you've managed to silence Cortana), seems to be stuck in a loop with no option to join a domain.
Do I need to create a machine admin first, before I can join it to a domain?
When selecting to [use the machine for work], it says sign in with Microsoft.
Then when you choose [Join domain instead] it says choose a name and password or [even better, use an online account]. Well I don't want to do either.
I left the office earlier with an active terminal window running a script on a Centos 7 server. Now I've SSHing in from home and I want to see where it's got to. Is this possible? Can I rejoin the same terminal window from here?
I help run three businesses, and we use two Exchange servers (Windows SBS) for basic email and file sharing. These seem to take up a lot of admin time when contrasted with the linux file server we have, which basically "just works". Is this because I'm inefficient, or because Windows SBS inherently requires a lot of admin time?
I'd estimate I spend two man-weeks per year, per server to admin these boxes, and we have fairly minimal requirements - around 20 staff in total. Based only on the time I spend, the 20 workers, and the two servers, is this 160 man hours per annum a reasonable amount of time?
I do all the admin such as adding and removing maybe 4 users per year, emptying out log files clogging the server, installing updates, resetting passwords when needed, setting up spf/dkim/transport, spam filtering etc rules. 90% of it is down to email/exchange admin.
Our Centos 7.1.503 server, running Netatalk recently ran to full disk capacity and our macs couldn't save files. I rebooted it and removed some (non-system) files but now the Netatalk share isn't available on the network. What's the procedure for diagnosing this problem and fixing it?
To complicate matters we recently moved premises and changed routers, although the server has been working in the new environment so I doubt this is an issue; although it's conceivable it's changed IP addresses I guess.
The server appears as "localhost" on the network and it appears to be pingable from the network, on the IP address it claims to be using. But clicking on localhost and trying to connect doesn't reveal any of the mounted volumes. Selecting "connect As..." gives an error; "the server does not appear to be available - check the server name and IP address."
The server has Internet and network access.
We have less secure authentication enabled on the clients. The volumes are mounted and browsable from within the server console.
systemctl-list-unit-files -t service
reveals avahi and netatalk are running
Any ideas what has broken, or steps to proceed with a diagnosis? What services need to be running for starters, and where do I check which volumes are shared on the network?
I also vaguely remember linking Netatalk to a certain Ethernet adapter; perhaps this has changed during the move?