Software Deployment Issues

Comments

8 comments

  • Shane Corellian

    Hi Justin,

    If you downloaded Adobe Flash from the Package Library it should attempt to deploy an MSI, not an EXE. 

    FlashPackageMSI.png

     

    If a package is stuck on Running then the problem is usually due to incorrect parameters being passed. Does the Flash package look like the image above (if you're running free mode Steps 2 and 3 will be disabled)

     

    0
    Comment actions Permalink
  • Justin Ngayan

    Hi Shane,

    I apologize...it actually is an msi file from the package.  After additional troubleshooting, I realized that the deployments were (mostly) successful to PCs hardwired into the LAN.  I was able to deploy exe files as well.  However, those that are wireless are not receiving the packages at all.  The difference between our LAN and WLAN speeds are only about 10 Mbps, so I can't see why the files are failing altogether (unless there are some timeout parameters that I need to set somewhere?).  The remote repair on the wireless PC obviously fails every test...so it's no question that this is isolated to wireless clients.

    Another weird issue is on one of my hardwired domain PC's; it keeps failing on an exe deployment and returning the message "The account name is invalid or does not exist, or the password is invalid for the account name specified."  This is the same PC was was able to receive two other pushes, but all of a sudden is returning this message.

    Any thoughts/suggestions to either of my issues?

    Regards,
    Justin

    0
    Comment actions Permalink
  • Shane Corellian

    Hi Justin,

    It could be that DNS hasn't been updated with the new wireless IP Address. From the console machine run this command:

    nslookup NWT-ADMIN2
    nslookup NWT-ADMIN2.newwave.com

    Does the same IP Address get returned? Is the IP Address the correct wireless address?

    If it is then it is possible, I suppose, that the target isn't running the Domain group policy. Refer to this forum post. Instead of editing the Domain Profile make the changes on the Standard Profile. Do this from the client PC (run gpedit.msc). After you make the change run this command (on the target PC)

    gpupdate /force /target:computer

    After you run gpupdate try the deployment again. Any luck?

     

    0
    Comment actions Permalink
  • Justin Ngayan

    Hi Shane,

    nslookup returns the same IP address and it is the correct wireless address.  I made the Standard Profile changes as suggested, ran gpupdate, and still the deployment failed.  It is saying the the PC is offline, and again all the remote repair tests failed.

    Justin

    0
    Comment actions Permalink
  • SelfMan

    Are you able to manually access the remote machine's admin share? i.e. \\<remoteip>\admin$

    0
    Comment actions Permalink
  • Justin Ngayan

    From my admin computer, I am not able to access the remote PC's admin share.  I am only able to access that admin share for that remote PC when I am physically at it.  Just to reiterate, I have Windows Firewall turned off, my network firewall has the necessary ports opened, I have made the standard profile changes as suggested, PC is pulling the correct IP, remote desktop connection works properly (just to prove that they are able to communicate to each other on the domain), and the deployments work fine hardwired, just not wirelessly.

    Just for testing purposes, I plugged in the LAN cable and disabled the wireless adapter on the remote PC and I was able to access the admin$ folder remotely from my admin PC.  This issue is isolated to wireless.

    Now, I just released and renewed the IP address.  Although it is still pulling the same IP address after, I was able to wirelessly access the admin$ folder.  I redeployed the software, but it just sits at "Running."  Not sure what else I can do at this point.  I checked the event logs on the remote PC and I do not see anything about the software deployment pushing.

    0
    Comment actions Permalink
  • SelfMan

    What are you using as your wireless access point? Do you have the latest firmware installed? Have you checked the firewall rules on that device?

    0
    Comment actions Permalink
  • Justin Ngayan

    Sorry for the delayed response.  Our WAPs are DAP 2553's, they all have the most current firmware, and we are not using firewalls with the devices.  We only have one firewall within our network.

    0
    Comment actions Permalink

Please sign in to leave a comment.