Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

winoutreach5

Member
  • Content Count

    31
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About winoutreach5

Profile Information

  • OS
    none specified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. When you apply the image to the other machines are you using a USB to Ethernet dongle with those deployments also? Is the USB port on the Panasonic a USB3 port by chance? Also, according to the article I linked previously, you should remove the AppX package for the user that is going to run sysprep first and then remove the provisioning to ensure the configuration is correct. From your most recent response, it is clear that you are removing the provisioned apps but it appears that you may not be removing them for the admin user first. Again, in the article I linked above, under the “resolution
  2. Just a thought after re-reading this – are you editing the Windows 8.1 image by chance? Are you updating apps or removing certain apps prior to your sysprep / capture? The reason I ask is because of this Microsoft support knowledge base article which provides 3 possible scenarios and offers a potential resolution. Another thought I had came after I read that you were using a USB to Ethernet dongle which brings a concern of a driver issue into play. From within MDT, you might try to create bootable USB media and use that to deploy your image to the Panasonic. If that works then you might take a
  3. You’re welcome. Again, I would strongly suggest checking out the logs for any indication into why the deployment might be failing. If there is an existing recovery partition on the hard drive you might want to clear that out in case the RE partition is causing the deployment of the image to fail. Another thought is if there is a driver that is interfering. Can you try to deploy the image without any drivers and see if the ToughPad accepts the driver-free image? Presuming that the issue does lie within the driver store there are a few things you will also want to check; there are three steps in
  4. Depending on where your deployment is failing we might be able to check the logs for insight into why. Since it appears that your deployment is failing during the specialize phase of Setup, you will want to check the setuperr.log file which is typically found in the %windir%\panther\ directory. More information on where log files are located can be found on in the TechNet library articles, ‘Deployment Troubleshooting and Log Files’ and ‘Windows Setup Log Files and Event Logs’. In the second article, we can see that the %windir%\panther\ location typically contains log information the correlate
  5. Dogway, When looking at some of the logs and error messages you are receiving I have to wonder what you are trying to accomplish by using 3rd party tools for your deployment that you wouldn’t be able to from the available Microsoft tools. You might want to check out the Microsoft Deployment Toolkit (MDT). First, it’s free and it can handle all your deployments including Windows XP, Windows 7, Windows 8, Windows Server 2003, Windows 2008 and Windows 2008R2. Using MDT, you can easily add both applications and drivers, manage Windows updates, create task sequences, join a domain, add a KMS or MA
  6. When using MDT you will find that there is not a need for slipstreaming as you can create task sequences to handle any post installation task such as applications or Windows Updates. To start, you can create a Sysprep and Capture Task Sequence which will do exactly what it says in the title -- it will sysprep your image and then proceed to capture it for use with deployment. Next, you can create a new standard client task sequence for the newly captured image of your reference machine and you can add all your necessary settings such as domainjoin, systemlocale, time zone, etc. Then you can the
  7. You might want to consider building this image with the Microsoft Deployment Toolkit (MDT) rather than manually because with MDT your drivers can be managed automatically which will in turn remove all the guesswork from the task. There are some drivers which do not play as well with DISM as others, particularly those with dependencies beyond the .inf files. First, aside from being free, MDT acts as a common console and can handle all of your deployments and it allows you to create various task sequences to accomplish your imaging and deployment goals / needs. To start, you can create a Sysprep
  8. In the event that you do want to block certain applications, or require certain restrictions for apps from the app store, another option is to take a look at AppLocker because it was updated for Windows 8 and you can use it to deploy an application control policy. In the above library article you will note that the first bullet point is, “Help prevent malicious software (malware) and unsupported applications from affecting computers in your environment” which may help you to feel as though you have more control over the apps in your environment. As you will see in the in this Microsoft KB ar
  9. If you’re interested, you might want to check out the Windows 8 Page on the Springboard Series site on TechNet as there is a free 90-day evaluation trial for Windows 8. This way, you can test out Windows 8 for yourself and see how it works on your current hardware and with your current applications. Let us know how it goes! Jessica Windows Outreach Team – IT Pro
  10. You might want to check out the troubleshooting section of the Basic Windows Deployment Step-by-Step Guide from TechNet. About a fourth of the way down the page you will find the instructions for how to disable driver signature enforcement. You also might want to check out the Deliver and Deploy Windows 8 page from the Springboard Series on TechNet for the above resource as well as several more that will help you push out Windows 8. Hope this helps! Jessica Windows Outreach Team – IT Pro
  11. Unfortunately, it is not entirely clear what you are trying to accomplish here. If you want to manage roles and features for computers running Windows Server 2003, Windows Server 2008, and Windows Server 2008R2 from your Windows 7 or Windows 7 SP1 machine then you will want to install RSAT which is available for download here. You also mentioned that you had already installed AD LDS for Windows 7. I first would recommend reading the AD LDS Getting Started Step-by-Step Guide and then the Installing or Removing Remote Server Administration Tools for Windows 7. Additionally, you might want to ch
  12. The first step would be to ensure you are using the latest driver for the hardware and operating system. According to this page on the Areca Support and Downloads page for Windows, the latest Windows 8 / Windows Server 2012 drivers were released on December 21, 2012 for 32-bit and 64-bit architecture. I realize you are deploying Windows 2008R2 but as noted in the latest Windows PE Overview Windows PE 4.0 was built on the Windows 8 kernel. With that said, it may be experiencing compatibility issues with a driver that was written for Windows 7. The next step would be to remove the driver in an
  13. The questions Tripedacus asked are important so that we know your current setup and hardware. Typically speaking, if your SSD is empty, you will just want to leave the space on you SSD unallocated and allow Windows 8 to format it and create the necessary partitions for you. If you could respond to Trip’s questions as well as include the model of a computer you are installing Windows 8 on, that would be very helpful. Additionally, you might want to check out the Windows 8 page on the Springboard Series for additional resources and guidance in regards to Windows 8. Jessica Windows Outreach Tea
  14. Cluberti makes an excellent recommendation. For the kind of scenario you are describing, you will really want to consider the use of deployment and imaging tools. MDT, or the Microsoft Deployment Toolkit, is free and can handle all your deployments including Windows XP, Windows 7, Windows 8, Windows Server 2003, Windows 2008 and Windows 2008R2. Using MDT, you can easily add both applications and drivers, create task sequences, join a domain, add a KMS or MAK product key, create an administrator account, specify time zone, etc. You can also import all user data into the new environment using th
  15. So happy to hear you were able to work it all out! Jessica Windows Outreach Team -- IT Pro
×
×
  • Create New...