T3chGuy007

Member

Last active 2 weeks ago

  1. 2 months ago
    Mon Jun 4 14:42:07 2018
    T3chGuy007 posted in Multicast Not Starting.

    I looked in Windows Firewall with Advanced Security on the server and there were several entries for udp-sender in the inbound and outbound rules that were outdated from when CrucibleWDS was installed. So I removed all the udp-sender rules from inbound and outbound rules and then ran your two scripts. I then tried to multicast but it still didn't work. So under each rule under inbound and outbound, I changed the path to the udp-sender.exe from "{app}\web\private\apps\udp-sender.exe" to "%ProgramFiles% (x86)\clonedeploy\application\private\apps\udp-sender.exe" and now multicast works. Thanks for all of the suggestions!

  2. Mon Jun 4 13:34:41 2018
    T3chGuy007 posted in Multicast Not Starting.

    I first changed the IP on my CloneDeploy server to be on the same subnet as my clients but that still didn't work. So I turned off the Domain profile firewall on the server and that fixed it. Now I need to figure out why the firewall was blocking the mulitcast. Thanks.

  3. Thu May 31 19:08:07 2018
    T3chGuy007 posted in Multicast Not Starting.

    I checked and I'm not even able to start a multicast with one device. I'm going to check with our network team.

  4. Wed May 30 15:36:35 2018
    T3chGuy007 started the conversation Multicast Not Starting.

    Hello. Today I began the process of reimaging my labs but I am running into an option with multicasting. I add computers to a group in CloneDeploy, assign an image, and then start a multicast of the group. All of the members of the group join the multicast session but the reimaging process never starts. My server and PCs are on different subnets but I don't remember this being a problem last summer when I reimaged my PCs. I verified that I am able to start an on-demand deploy and it works just fine. I am running CD 1.3.5. Any suggestions? Thanks!

  5. 3 months ago
    Fri May 18 20:23:33 2018
    T3chGuy007 posted in Renaming PC Not Working.

    I believe I found out why v1803 was not renaming the PC correctly. When I built the reference image for my live environment, I set the name of the PC to what it was going to be called in AD after my reference image was deployed to it. In my test environment though, I left it with whatever random name Windows used when I did the clean install of v1803. Apparently, in v1803, if the computer is configured with the same name as specified in your .xml file, it skips renaming it and applies a random name. If the name of the PC is set to something random, then during OOBE, it will change it to what you have specified in your .xml.

    I verified this works because on the PC in my live environment, I renamed it to something random, ran sysprep, shutdown the PC, uploaded the image, and then deployed the image. After the deployment was finished, the PC was joined to my domain with the correct name. In my test environment, I changed the PC from the random name to the name that was specified in the .xml and after I deployed the test reference image, it was joined to my domain but with a random name. I also verified that if the name of the PC is set to what it was going to be called in AD and the PC is running v1703, it still renames it. This must be a change in v1803.

  6. Fri May 18 15:04:03 2018
    T3chGuy007 posted in Renaming PC Not Working.

    Ok. I replied to this post to the TechNet post to see if we can get some answers.

  7. Fri May 18 14:21:58 2018
    T3chGuy007 posted in Renaming PC Not Working.

    I checked C:\Windows\Panther\unattend.xml and the computername is listed correctly. It shows the same name that is listed in CloneDeploy. However, the actual computername is listed as something completely different. It appears to be a random name. If I manually try to rename the PC, it allows me to do it so I don't think there's a conflict in the name when it attempts to change it after it's been deployed. Are there logs files that I can look at to see why the computer was not renamed correctly?

  8. Thu May 17 16:39:14 2018
    T3chGuy007 posted in Renaming PC Not Working.

    Ok, here's an update for you. I first deployed last year's uploaded image, which is Windows 10 v1703 x64. Everything went fine because the computer joined to my domain and it was named correctly. I then modified the profile associated with the v1803 image so it does not change the computer name(Image Name->Profiles->View->Deploy Options, unchecked 'Change Computer Name'). I then deployed this image to the same PC and this time, it was joined to my domain and the computer name was set to CLONEDEPLOY. I used the same .xml this year as I used last year. The only difference that I can think of is that I'm trying to deploy v1803 this year instead of v1703.

  9. Thu May 17 14:14:11 2018
    T3chGuy007 started the conversation Renaming PC Not Working.

    Hello. I've started to build and deploy my PC images for the summer and I came across an issue that I wanted to get some advice on. I've been using the same unattend.xml file since 2016 and this morning, I tried to deploy an uploaded image to a PC and everything went well except that it didn't rename the PC. Instead, it renamed the PC to a random name. I have an unattend.xml file located in C:\Windows\System32\Sysprep\ and inside the .xml, under the Specialize pass, I have a the tag <ComputerName>CloneDeploy</ComputerName>. After the image has finished deploying to a PC, i see the following messages appear so I believe the .xml is set up correctly. Any suggestions as to why the renaming isn't taking place? I'm using Windows 10 v1803 x64. Attached is my .xml. Thanks!

    **Changing Computer Name On /dev/sda2**
    mkdir: cannot create directory '/mnt/ntfs': File exists
    ...Found Answer File At /Windows/Panther/unattend.xml, Changing Computer Name.
    **Closing Active Task**

  10. last year
    Tue Jun 6 19:54:57 2017
    T3chGuy007 posted in Multicast Throttle.

    Worked like a charm! I went from 4GB/min to around 650MB/min and the other devices aren't being bogged down. Thanks so much!

View more