Do they even have control over that? I always got the sense the updates were pushed by NMCI remotely.Wish our IT shop would ensure computers are updated at 0300 and not when everybody is at work and pilots need to log SHARPS/NAVFLIRs
Do they even have control over that? I always got the sense the updates were pushed by NMCI remotely.Wish our IT shop would ensure computers are updated at 0300 and not when everybody is at work and pilots need to log SHARPS/NAVFLIRs
Some. There are ways you can check on individual computer patch status to verify that it did happen automatically. If it didn't happen automatically then theyd have to manually pull the updates to the machine. If that fails then you call NMCI and it can end up with field services taking the machine away for a reimage.Do they even have control over that? I always got the sense the updates were pushed by NMCI remotely.
In 2008 when I was on my IA in Iraq, one evening at the daily ops update, the SIGO announced that the IT people were doing theater-wide system maintenance the middle of the next day and SIPRNET would be down for an hour or two during the middle of the day. At that moment I learned me everything I've ever needed to know about military IT's understanding of what "supporting vs supported roles" means. Any "hmm" moments about Navy IT and any GMT the Navy made me do, before or since, has merely reinforced that lesson.Do they even have control over that? I always got the sense the updates were pushed by NMCI remotely.
Do they even have control over that? I always got the sense the updates were pushed by NMCI remotely.
Yikes. That's a lot of profile bloat on those HDs.I am fairly sure the green shutdowns happen to all our computers daily. Generally when somebody signs off, they get the, "WANNA DO A GREEN SHUTDOWN AND F*CK YOUR BUDDY?!" dialogue, which nobody clicks (unless by accident) since it'll down that station for an hour. Since we just leave the computers on when we're done with them, I'd be surprised if IT couldn't set up an "auto-restart with a green shutdown" policy in the middle of the night.
A wardroom of nearly 60 JOs sharing four computers would deeply appreciate it...
Yikes. That's a lot of profile bloat on those HDs.
I couldn't find one when I looked a couple weeks ago. Would love to hear if someone has figured it out!Isn't there an S/MIME solution? I remember seeing some stuff a few months ago that was supposed to make it work on OWA.
I had one for use on an NMCI machine using OWA w/out VPN. No idea for USAF on your personal machine. Lots of stuff on the interwebs and it's received a lot of attention lately with so many on TW.I couldn't find one when I looked a couple weeks ago. Would love to hear if someone has figured it out!
Yikes. That's a lot of profile bloat on those HDs.
You’ll be happy to know that AF internet isn’t any better, but they did program into the AF system that every time you log in the computer says “Good morning/afternoon/evening insanebikerboy”. So, at least they politely welcome you to the suck.
Most likely, the issue is that everyone who has ever logged into that machine, the machine built a user profile for that person (which sits on the disk forever). Without troubleshooting your exact issue, for most “slow” Navy shared computers I think it’s probably that, versus any Navy background-run spyware.This raised my blood pressure yesterday. Spent two hours across six machines trying to log on. My favorite is that our SIPR machine will occasionally lose connection to the keyboard due to the KVM switch, and the only solution is a restart. So I restarted, and it booted straight up into a Green Shutdown (these take 5-45 minutes, depending on your gods).
Animal rage.
The thing that gets me is that 8GB of RAM should be plenty, but the computers will FREQUENTLY boot up to black screens with operable cursors, requiring the user to manually execute "explorer.exe" to attempt to run the OS. That will usually fail. I don't know what the Navy's got running in the background of these computers, but the computers at my current command are worse than any I've encountered on the ships or elsewhere.
My IT guy told me today that our 8 GBs of RAM per desktop could be upgraded up to 64 with Wing approval, but that it would also be very unlikely due to the process involved. Wish he hadn't said anything.
I'm kind of surprised that the ACDU side hasn't transitioned to issuing at least all Os their own computer. Funding and all that likely prevent it but at NAVAIR we all get issued a computer from our homeroom. If we change homerooms there are ways the computer can or cannot be transferred but your profile is still there and now OneDrive. I have my own computer that I can walk around with, use enterprise WiFi on if the buildings have it, or travel, go to off-site meetings, or TW via hard-line or wifi+VPN. Every couple of years someone comes by and gives me a machine (and another keyboard and mouse, they're piling up). This is all built in to our homeroom overhead/rate.