Jump to content
DeployCentral

BB IT

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About BB IT

  • Rank
    Member

Recent Profile Visitors

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

  1. Thanks to Jeff and his coworker I've got my server up and running again. It was either a missing MS update or because my region locale isn't fully supported that caused the issue.
  2. Hi, Sorry! Brainfart on my behalf. I was running with the old image, as I've had issues with my deployment server all week, and hadn't updated to the new image with the platform pack...
  3. Hi, We have just recieved 6 Dell Precision 5530 with USB-C thunderbolt docks. I have activated the thunderbolt support functions in the BIOS, and I can PXE boot into SmartDeploy, but the PC never recieves an IP address afterwards. What's the best way to fix this?
  4. Hi Jeff, It made no difference. I'm still getting the same errors as above.
  5. Hi, I have created a ticket now.
  6. Hi, After updating to version 3010 I'm now getting the following errors: "Unable to connect to the SmartDeploy Console service" followed by "There was no endpoint listening at http://localhost:8734/Design_Time_Addresses/SmartDeploy.ConsoleServiceSLWCF/Message/ that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException , if present, for more details." There is a ton of SQL error logs in the EventViewer (I can send the logs if necessary). There seems to be no problems with deploying from my images, though. Any idea what could be wrong?
  7. Hi, I've just been through the following troubleshoot, and was wondering if someone else have had the same issue. In that case I'll share my experience and solution: We just bought some 30 E5590 laptops to roll out a workstation upgrade for our users. The image deployment goes well until the mandatory BIOS upgrade from the platform pack kicks in. The laptops come with 1.0.8 out of the box, and is upgraded to 1.1.9 during the deployment. Right after this upgrade the PC reboots, and I was met with a "No boot device found" screen. In the BIOS the UEFI boot manager is missing from the boot sequence. When I added it manually, and pointed to the specific EFI boot manager from the deployed OS, I was now facing a corrupt OS message (couldn't be repaired with Win10 from a USB). I also noticed the SSD was present in the legacy devices of the boot sequence before the BIOS upgrade, but was now missing from the list after the upgrade. What I tried: Switch from legacy to UEFI boot (and vice versa). Upgraded BIOS to 1.2.3, and downgraded to 1.0.8. Changed drive settings from RAID to AHCI and redeploy the image. In the end it turned out I had to activate the UEFI PXE settings on the NIC in BIOS, and redeploy the image once more. Worked like a charm right after. As I have not seen this specific issue mentioned in any of the SmartDeploy documentation I thought it could be worth sharing with the community.
  8. I did open the applications on my first image to check that our add-ins were installed correctly (and then I read the user guide), but on the second image I created after wiping the VM, I never touched it. I'll try reinstalling it with the link you provided. Thanks.
  9. BB IT

    Deployment isues

    Just in case someone else have this issue: Glenn provided the following solution: 1) Open your answer file with a text editor 2) Search for " <network_share>" 3) Change the drive letter to something else that you do not normally use and save the changes 4) Recreate your media
  10. Hi, We are using the Microsoft E3 suite for our users, and I have to run an online repair of Office 365 after each deployment due to the "this app can't run on your pc, to find a version for your pc, check with the software publisher." error. I've followed best practice section on page 13 in the user guide for every built/rebuilt of my images, but the issue still persists. Have anyone got it to work, and what exactly did you do? It's not that much of an issue, as it usually only takes 20 minutes, and I can finish up other tasks in the meanwhile, but it would be nice to have it fixed
  11. Yeah, I was afraid of that, though I did have a weak hope of it being a feature I had overlooked, since the User Migration setting already use USMT. Maybe it should be a requested future feature to incorporate that fully in the later SD updates?
  12. Hi, We are about to replace some fifty PC's in our company, and I was wondering if it's possible to use SD to migrate user data (and hopefully the applications we do not provide as standard in the image) from one PC to another?
  13. BB IT

    Deployment isues

    Nevermind. Tried it again on a different PC and different UPD port, and now it just works. The IT gods works in mysterious ways...
  14. BB IT

    Deployment isues

    Hi, I'm having a weird issue when deploying an image. I have a clean Win 10 image that has been through the SD mill, and can be deployed with no issues. Then I have the same image after installing my software, but whenever I try to deploy it I'm asked to specify the network path, and manually choose my new image. Both images have the same settings in the answer file and during the media creation. I have triple checked the credentials. The only difference is that my first image was created before I upgraded SD to version 2.0.3000, while the other was created today. What gives?
  15. Everything works like a charm now. Thanks for the help, and have a good easter.
×