After last nights ForeFront update our XP machines will not work.
Have anyone else experienced this.
--
T. Todd Lemmiksoo
They won’t work at all? Or, just the Endpoint Protection client?
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Todd Lemmiksoo
Sent: Wednesday, April 16, 2014 9:08 AM
To: ntsysadm@lists.myitforum.com
Subject: [NTSysADM] XP issue after Forefront
The PC's freeze on the login or startup process.
On Wed, Apr 16, 2014 at 8:27 AM, Rod Trent rodtr...@myitforum.com wrote:
They won’t work at all? Or, just the Endpoint Protection client?
*From:* listsad...@lists.myitforum.com [mailto:
listsad...@lists.myitforum.com] *On Behalf Of *Todd
The boxes in question are all housed in a top-tier hosted data center with
biometric scanner and audited access. The biggest concern is logical
security.
The goal is to prevent someone who gets access to the master box, and thus
has automatic authenticated access to several other key systems
I have to agree an abuse of trust from one trusted services to others would be
a control point that I would look at within the system. (I am not sure is this
is based on Service Orientated Architecture type of system or something more
simplistic).
The 2 factor is definitely a good start up
Just got word…
http://windowsitpro.com/windows-xp/windows-xp-hangs-after-latest-forefront-endpoint-protection-update
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Todd Lemmiksoo
Sent: Wednesday, April 16, 2014 9:37 AM
To:
Whoa. Nifty.
http://www.championone.net/products/transceivers/sfp-2/single-fiber/
-Paul
Hmmm, accident, or planned?
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Rod Trent
Sent: Wednesday, April 16, 2014 7:15 AM
To: ntsysadm@lists.myitforum.com
Subject: RE: [NTSysADM] XP issue after Forefront update
Just got word…
An accident brought about by not being required to test on an unsupported OS.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Heaton, Joseph@Wildlife
Sent: Wednesday, April 16, 2014 10:24 AM
To: 'ntsysadm@lists.myitforum.com'
Subject: RE:
However, reports are also coming in about Windows Server 2003 R2 having the
same issues, and that OS doesn’t reach end of life until July 2015.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Rod Trent
Sent: Wednesday, April 16, 2014 10:35 AM
To:
What, Server 2003? J
Steve Cain
Sr. System Administrator
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Rod Trent
Sent: Wednesday, April 16, 2014 10:35 AM
To: ntsysadm@lists.myitforum.com
Subject: RE: [NTSysADM] XP issue after Forefront
Ok, I went through the process on the link you provided:
- downloaded the offline installers.
- ran the Fix Windows Update
- ran the Scan Windows system components sfc /scannow
- removed the KB2919355 package
- cleaned up the WinSxS folder
- restarted
- ran the KB2919355 - successful
- ran the
Microsoft released a botched update, it killed every XP workstation we have and
wasn’t nice to 2003 servers either. We are running SCCM and SCEP 2010. Go
figure the week after support ends they decide to break it.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
FYI: The pre-release definitions will solve the problem.
Article updated:
UPDATE: I'm also being told (thanks http://twitter.com/@bartsurminski Bart
Surminski!) that a beta version of the definition will also fix this. You can
download the definition beta here:
On Wed, 16 Apr 2014, Andrew S. Baker wrote:
Hey, with XP not being supported, there's no need to test against XP. :)
XP is still supported.. it's just not free anymore..
This is one way to drive up purchases of support contracts...
-sc
-Original Message-
From: listsad...@lists.myitforum.com
[mailto:listsad...@lists.myitforum.com] On Behalf Of Joe Smith
Sent: Wednesday, April 16, 2014 11:13 AM
To: ntsysadm
Subject: Re: [NTSysADM] XP issue after
This is also happening with MS Security Essentials.
On 4/16/2014 9:37 AM, Todd Lemmiksoo wrote:
The PC's freeze on the login or startup process.
On Wed, Apr 16, 2014 at 8:27 AM, Rod Trent rodtr...@myitforum.com
mailto:rodtr...@myitforum.com wrote:
They won’t work at all? Or, just the
Given our experiences with UAG over the last couple of years, I'd say they quit
testing with XP a looonnng time ago. :)
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: listsad...@lists.myitforum.com
But at least the prices went down.
http://www.infoworld.com/d/microsoft-windows/microsoft-slashed-windows-x
p-custom-support-prices-just-days-axing-public-patches-240623
Steve Cain
Sr. System Administrator
-Original Message-
From: listsad...@lists.myitforum.com
If I run dotNetFx40_Full_x86_x64.exe /q /norestart /log
%temp%\dotNetFx40.log manually via a command line on a Win7x86 machine, it
runs great.
However, if I add the app to MDT with the exact same command line, it hangs.
The application install bar says it's installing, but stalls. It will
It's negotiated on a per-company basis, and based on several factors
including aggressive migration schedules. Extended support costs will go
down if the company enlist (pay for) MCS to help with the migration.
So, I'm not sure they really lowered their prices as much as those companies
being
Also just to add - one of the possible fixes on that site is to add a System
Tools folder to C:\ProgramData\Microsoft\Windows\Start Menu\Programs if the
folder isn't there. In my case, it's not there but when I add it it
immediately disappears.
Jay Dale
Director of Information Technology
Do you have the ability to open a support case? If not, holler and I'll
set one up for you.
And by the way:
Microsoft gives business users more time to install Windows 8.1 Update |
ZDNet:
a work-around (though not the best approach) is to start in safe and disable
MSE service
Jean-Paul Natola
From: rodtr...@myitforum.com
To: ntsysadm@lists.myitforum.com
Subject: RE: [NTSysADM] XP issue after Forefront update
Date: Wed, 16 Apr 2014 11:11:34 -0400
FYI: The pre-release
Beyond extra login security for the master (perhaps going to RSA or other
fob, plus challenge/response to phone), I'm not sure what extra could be
done.
IPSec between master and minions, in addition to SSH? Seems like overkill,
and pretty cumbersome.
Kurt
On Wed, Apr 16, 2014 at 6:44 AM,
I don't have the ability (or the funds) to open a support case.
Just another note - the System Tools folder is already there, but it's called
Windows System and it's shared out as System Tools...FYI...
Jay Dale
Director of Information Technology
P:713-333-2020
-Original Message-
Have you tried to run full malware scans from several different scanners?
Something like Malwarebytes and Vipre to determine if the machine has a bug
hidden in the system some place causing issues? I had this happen a while back
with an XP or Windows 7/Vista machine. Once the bug was cleaned
To be clear to everyone, this update - because it's deemed mandatory and
a security update there's a no charge. That said you sometimes have to
put in a credit card - that they don't charge - to get a case opened.
But ultimately it's a free case. Sometimes it's just hard to get into
the
28 matches
Mail list logo
