Deploystudio Mac Network issues
Hello I am using Deploystudio to image Macs. I had gotten close to having 1 image for everything we owned until we moved to 10.10.x I am now faced with an issue where the MacBook Pros and iMacs are not configuring Network ports correctly. I believe this is because the Ethernet on these are EN0 and the image was made on an air where the WiFi is EN0. Is there any way to get these setup with a post imaging script where I can determine which physical adapter is which and set just DHCP to the physical and SSID, Password and DHCP to the WiFi?
What do you mean by "are not configuring Network ports correctly?" What is happening?
Also, I am not exactly sure what you are wanting the post script to do. Could you clarify that a little?
Also, I am not exactly sure what you are wanting the post script to do. Could you clarify that a little?
ASKER
Image created on MBAir will restore fine to the MBAir. It has Wifi at EN0 and Thunderbolt at EN1. I configured Wifi for our SSID and all images get it.
I used to be able to use the same image on the MBPro and iMacs and get the same result however after going to 10.10.3 I see that the MB Pro is using the "WiFi" designator for the Ethernet port and getting DHCP from the wire and I have no connection to Wifi. I would like a way for all the machines to use the same base image and automatically set DHCP on the Ethernet and Thunderbolt ports and set the SSID, Password and DHCP for the Wifi.
It worked before and I am not sure if it was Deploystudio or the OS change that broke it. I am not real great with Macs and inherited the Deploystudio so my experience is probably lower intermediate in this area. My best guess is something used to adjust for the Airs being EN0 = Wifi and MB Pros and iMac being EN0 = Ethernet. If it were scripted I could image no network settings and run a script to put the right configuration on the right hardware port. But I am only grasping for solutions and am open to anything that works while preferring not to do the obvious and have seperate images for each hardware type as they are harder to maintain.
I used to be able to use the same image on the MBPro and iMacs and get the same result however after going to 10.10.3 I see that the MB Pro is using the "WiFi" designator for the Ethernet port and getting DHCP from the wire and I have no connection to Wifi. I would like a way for all the machines to use the same base image and automatically set DHCP on the Ethernet and Thunderbolt ports and set the SSID, Password and DHCP for the Wifi.
It worked before and I am not sure if it was Deploystudio or the OS change that broke it. I am not real great with Macs and inherited the Deploystudio so my experience is probably lower intermediate in this area. My best guess is something used to adjust for the Airs being EN0 = Wifi and MB Pros and iMac being EN0 = Ethernet. If it were scripted I could image no network settings and run a script to put the right configuration on the right hardware port. But I am only grasping for solutions and am open to anything that works while preferring not to do the obvious and have seperate images for each hardware type as they are harder to maintain.
ASKER
More pieces to the puzzle. The base 10.10.3 image was built on a new MacbookAir. I cannot load the 10.10.2 image on these new Airs.
As a test I restored the 10.10.2 image to a mid 2013 Mac Air and it works as does the Macbook Pro.
In other words with a single 10.10.2 Image created on an iMac using EN0 for RJ45 Ethernet and EN1 for Airport/Wifi I restore to a MacAir using EN0 for Airport and EN1 for Thunderbolt. It all immediately connect to a password protected SSID without any user/admin intervention.
My issue seems to be with the new MacAir Hardware (Early 2015) being compatible or an issue with deploystudio and this new hardware. I am continuing to look at this and learn as I go. Any insight is appreciated.
As a test I restored the 10.10.2 image to a mid 2013 Mac Air and it works as does the Macbook Pro.
In other words with a single 10.10.2 Image created on an iMac using EN0 for RJ45 Ethernet and EN1 for Airport/Wifi I restore to a MacAir using EN0 for Airport and EN1 for Thunderbolt. It all immediately connect to a password protected SSID without any user/admin intervention.
My issue seems to be with the new MacAir Hardware (Early 2015) being compatible or an issue with deploystudio and this new hardware. I am continuing to look at this and learn as I go. Any insight is appreciated.
It does sound like a post script would be best. I do not have 10.10 so the commands may be slightly different.
I would try a script containing
I would try a script containing
networksetup -setairportnetwork en1 yourSSID yourpasswordASKER
EdTechy, I agree. It would need to also determine which port is the Ethernet vs the Wifi vs thunderbolt at the hardware level to get the en1 portion. That is where I am stuck.
ASKER
Then the script would have to add the correct service to each.
If you set the post script in Deploy Studio, it is easy enough to change it. Try en1 first then en0. I believe the service is hard coded in the hardware so one of the two (en1 or en0) in the script should get you connected to the wireless network.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is a hardware thing with Macs where the Eth0 is either the Wifi or Ethernet adapter based on the model. When using a generic image it works on both models but the Description of the MB Airs is Ethernet for the Wifi Adapter. Never figured how to change that so I am just excepting it.
ASKER