Jump to content

Search the Community

Showing results for tags 'xp'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Found 11 results

  1. WannaCry was a disaster that could have been prevented if people took notice. If you didn’t hear about it you must have been asleep, here is a refresher. After WannaCry, most businesses took notice and updated their operating systems, patched them and took measures to avoid a further outbreak. But today, May 14th, 2019, Microsoft has released information that warns of yet another WannaCry-like worm. Note: If you are using Windows 10, you are OK, you are not vulnerable to this CVE. If not, and if you are still on Windows 7 then start upgrading to Windows 10 by using the Inplace Upgrade Task Sequence I explain about here or if you cannot upgrade immediately, then patch Windows 7 to protect it from this vulnerability. Vulnerable in-support systems include Windows 7, Windows Server 2008 R2, and Windows Server 2008. Downloads for in-support versions of Windows can be found in the Microsoft Security Update Guide. Customers who use an in-support version of Windows and have automatic updates enabled are automatically protected. Out-of-support systems include Windows 2003 and Windows XP. If you are on an out-of-support version, the best way to address this vulnerability is to upgrade to the latest version of Windows. Even so, we are making fixes available for these out-of-support versions of Windows in KB4500705. If however you are running Windows XP, yes…. that old unsupported operating system then take warning ! Today, Microsoft has warned against the wormable capabilities from this CVE (critical Remote Code Execution vulnerability) and they blogged about what to do to avoid it happening to you. Read that blog post here: https://blogs.technet.microsoft.com/msrc/2019/05/14/prevent-a-worm-by-updating-remote-desktop-services-cve-2019-0708/ It’s very clear from their text that this is all about protecting customers from the next worm, so pay attention and if you have old operating systems that are in support and affected, then update immediately. Note: This is so serious that even Windows XP and Windows Server 2003 are getting updates from Microsoft for this vulnerability. You can download those updates from Microsoft Catalog here. https://support.microsoft.com/en-ca/help/4500705/customer-guidance-for-cve-2019-0708
  2. Ransomware has been around for a few years now but up until yesterday, it wasn't that well known about. This latest RansomWare called WannaCry has changed that for ever. Ransomware encrypted data on at least 75,000 systems in 99 countries on Friday. Payments were demanded for access to be restored. European countries, including Russia, were among the worst hit. Companies around Europe were hit and investigations are underway to see who was responsible. This was such a big attack that Microsoft released patches for unsupported operating systems (such as Windows XP) to allow those businesses still running them, a chance to protect themselves. Guidance available In addition to making patches available, Microsoft has published guidance to explain what is necessary in protecting yourself against this Ransomware and any others based on the same vulnerabilities (SMBv1). These vulnerabilities were patched by Microsoft in March of this year, but of course there were no patches (at that time) for unsupported operating systems such as Windows XP. Download Patches for unsupported Operating Systems To patch your unsupported operating systems, get over to this url and download the available patches. WannaCry has multiple vectors, but you should remove one vector, SMBv1. Do as follows 1. Block 445 inbound 2. Install MS17-010 3. Remove SMB1
  3. I am trying to build an XP image that will be pushed out to 'refresh' exisiting XP installed and these will become dumb terminals for RDP use only. The basic steps i am trying to follow are Create Deployment Share Add XP Operating system under Operating Systems Add Capture and Sysprep Task Sequence .. & so on I am unable to add XP as an Operating System and this is stopping me from creating the Task Sequence as you need to point to an imported OS during the wizard. Process - Right click Operating Systems > Import Operating System > Full set of source files > Browse to OS files > Error Import Operating System Wizard : Please fix all errors before continuing. The source directory sepcified does not contain an identifiable Operating System I have tried mounting OEM and non OEM discs, SP3 & SP2, copied install files from disc to folder.. I dont have a problem adding Win7 and up. Im running version 6.2.5019.0 which should support XP.. Any ideas?
  4. Hi, Upgraded SCCM to versions R2 and MDT Refresh task sequence starts to fail when started from XP. Does anybody have successfully launched Task Sequence from XP, Task Sequence fails to restart to Windows XP. So, the main question is, anybody succeeded performing Refresh from XP with SCCM 2012 R2? Thanks.
  5. Hi everyone, I have to migrate 8500 PC from XP to Win 7 (and later 8.1) using a fresh install of SCCM 2012 R2. My goal is to be able to use USMT to backup user's files on a SMP server and I would like to do this in Offline mode. As USMT 6.3 is incompatible with XP, I found this article and successfully managed to backup data using Online mode and 2 TS as explained. Now, I need to be able to do a MDT task that captures data in Offline mode using SMP and not Hardlink because I want to reformat every computer. Has anyone been able to do this and is willing to share his TS ? Is it even possible ? Thanks in advance.
  6. hi guys i'm doing a lab from the book System Center 2012 Configuration Manager: Mastering the Fundamentals by Kent Agerlund, and in it, there is a refresh to win 7 from xp lab using mdt integraated with config manger. I'm following the instructions exactly, but everytime i run the task sequence to install the os, im getting an error even before getting to boot to winpe. Everything seems to be running fine, but then the task sequence errors out with this message Task Sequence: Windows 7 ent x64 has failed with the error code (0x0000264C). For more information, contact your system administrator or helpdesk operator. Then in Software Center I see this error Error: 0x4005(16389) I examined the smsts log and only see this error Error getting system isolation info. Code 8027000C Remediation failed. Code 8027000C Remediation failed with error code 8027000c researching the error codes i dont find a lot of information, suggesting maybe it could be a driver issue. i didn't add any drivers to my boot image but I was able to get into winpe before and it was the same task sequence using the same boot image so i'm unsure if thats the reason for the error im using vmware workstation 9 and sccm 2012 sp 1. thanks to anybody that can help EDIT* Ok i resolved the above issue (memory wasn't set correctly) but now im booting in win pe and getting "unable to read task sequence configuration disk" and navigating to smsts log i see error failed to find the configuration path error 80070003 One person resolved it by updating the bios but im not sure if that is the issue
  7. I have two TS, one for known computers with allready installed the agent (migrate compname is on) and another for unknown computers, on this one you need to fill in the computer name during WinPE. This method works fine for Win 7 and Vista. On XP there is a problem: We work with a full operating installer in combination with an unattend.txt For allready known and unknown computers the compputername is forgotten and a dynamic name is given. How do i fix this? Please advise.
  8. Hello, I was hoping someone could help point me in the right direction. We are using SCCM 2007 and UDI Toolkit 12 to deploy new WIndows 7 machines through a task sequence. We are now trying to migrate from XP to Windows 7 using USMT 4.0. We are trying to do this through the PE environment. We have it successfully doing a scan state, however we run into issues when applying the new OS. I'll mention at this point we have PointSec full disk encryption running on these devices. If we do the scanstate and use the task sequence option to format and partition the disk. It fails as it says the files are protected, these are the ones protected by USMT. So all the xml files, working directory. I think it also protects areas such as boot. I've tried calling a disk part myself and doing a clean, delete of volumes and re-creating them. It then allows it to install the OS, however whenever it does its first reboot it says no OS is present. When I run diskpart its changed the volume to RAW and you cannot access the data. I've tried various combinations on running both types of formats/partitions cleans etc.. One thing I cannot make sense of is that we use the task sequence format and partition when we don't need to save data. So this just blows away XP with encryption and puts on Windows 7, i've tried using this same command but it doesn't have the same effect. Anyone able to help please? Thanks, Andy
  9. Hi, I'm having an issue while trying to deploy Windows XP SP3 from a captured image to a computer using SCCM 2012. All my Windows 7 deployments work great, but this one is failing. The problem seems to be during the Apply device driver point. In my environment, I've created driver packages for each of my hardware models and per operating system. I then do some WMI filtering to apply them. What seems to be happening is that SCCM imports them with a GUID as the directory name in the driver package. When it applies the drivers for that model and modifies the OEMPNPDriverPath line in the Sysprep.inf file, it exceeds the magic 4096 character length. No matter what I do, I can seem to get past this. Any one have any ideas? The machines that I'm using are Dell computers and I'm using the Dell Cab files imported and packaged. Attached is my smsts.log file Thanks smsts.log
  10. All, I am trying to deploy windows Xp via SCCM. I have SCCM set up correctly - It was working! Yesterday I added in 1 driver... It failed deploying so I thought "OK" and removed it from the package and updated the distribution point...... NOW - I cant build the machine that worked absolutely fine yesterday!! I have been through the SMSTS.log and the ZTIValidate.log which i've taken off the root of the machine thats failing. The machine fails just after applying driver packages - I have it set up so that it applies the HDD driver first - and then everything else! This is whilst being in PXE so network and HDD drivers allow this stage fine. I am unable to provide any screen shots or log reports as thats potentially damaging to my organisation - appologies. Any thoughts? Please help!
  11. Hello all, I'm using SCCM 2007 SP2 to do some test deploying of Windows XP SP1a to a Dell SX270 desktop machine. I've successefully deployed this package (minus the driver which I'll discuss in a minute) to a vmware virtual machine. For the, the package deploys and it does finish the installation of XP and seems to get to the point of bringing up the logon screen for windows, but it goes to blue screen with the mouse icon there that you can move around, but it doesn't respond to any keyboard pressing. I can restart the machine and it does come back up to the windows login screen, but it has not been added to the domain like the package was supposed to do. I am almost 100% positive that it has to do with the fact that XP SP1a does not have a compatibly network driver for the network card in the SX270 machine. In fact there is no network adapter under network connections when logging into XP. I've tried incorporating the driver by importing it into the SCCM 2007 driver library and also added it to the task sequence as a software package install, but still ending up with the same result. How do I get the driver to install in time for windows to use it when it needs during the installation? I would also like the package to go ahead and install XP SP3 while it's doing the deploy if you wouldn't mind giving advice on that as well. Any help would be greatly appreciated. Thanks.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.