Not Bad For Mac

• Not Bad For Macbook Pro
• Google Chrome Bad For Mac
• Not Bad For Macbook

The first reason you would get a BADMACIP error is if you have duplicate KUIDs trying to check in. This is because the K1000,by default, is set to detect duplicate assets and not allow them into inventory. Putting the amp agent directly intothe image you are using, rather than installing the amp agent post installation will cause this problem. There is ascript in the K1000 that allows you to reset your client KUID: K1000/Adminui Scripting Scripts Reset KUID. Also, you can manually reset the KUID by following the steps inthis article to delete the keys manually and have them re-populate: Here isanother article that addresses duplicate machines, disappearing inventory devices, and the over-arching question of duplicate asset management: Anotherreason we have seen machines not propagating inventory, while giving theBADMACIP error, is due to altering a virtual K1000's hardware resources. If youare dealing with a K1000 virtual appliance, you have the ability to alter theamount of resources that you allocate to the K1000.

Not Bad For Macbook Pro

If the hardware in the virtualappliance is reduced below 4 cores and 8 gigabytes of memory, you may run intoissues with provisioning. This isan example that I saw last week: I was provisioning a group of 130 computers that were all freshly imaged. After they were provisioned they wouldn't populate into the K1000 inventory. Furthermore, the K1000 log was showingthe error 'BADMACIP=xxx.xxx.xxx.xxx' for the computers that I was provisioning.

For years, Mac gaming has been almost an oxymoron - not really worth considering if your love of games extends beyond Football Manager. But things are changing. Big games are coming to Mac quicker.

They were not populating into the K1000 at all. This is what turned out fixing this issue: The Virtual K1000 was configured as such: OriginalHardware Configuration: (4) cores and (8) gigs of ram. The K1000 hardware was altered to: (1)core and (4) gigs of ram.This worked for a while until it reached roughly 1700 assets, then it startedthrowing out BADMACIP. The hardware for virtual K1000 appliance was then changed to: (2) cores and (8) gigs ofram, and then rebooted. This fixed the problem and all of the machines startedchecking into inventory. I would like to hear if anyone else has a weigh in tothis issue.

There are other possibilities that I haven’t been able to fullytest in my lab environment, like the possibility for this to be caused byIP/DNS related problems. Hi, I didn't find a resolution to this issue, but I found a work around and understand better the scenario when this happens. This only happens for Macs with an Ethernet bond.

Google Chrome Bad For Mac

The agent doesn't seem to be able to understand the IP address of the computer if there is a bond link in place. The amp.conf file does not contain an ip address for the Mac. If I add another network adapter to the Mac, such as a Firewire adapter (doesn't even need to be connected and live), and then gave this an IP address, subnet and gateway, then the amp.conf file would then contain an IP address and the agent would then check in to the K1000.

Not Bad For Macbook

As I say this is a work around for any Macs that have an ethernet bond and are running the agent. Hope this helps.