In case you are in search of the solution to this behavior, there is a fix (I recommend getting AW help for this) but here is what my specific problem was.
Upon executing the following query on our AirWatch Database:
select DefaultLocationID, LocationGroupID, t2.LocationID,t2.PrimaryLocationGroupID from locationgroup t1
left join location t2
on t1.locationgroupid = t2.PrimaryLocationGroupID
We found that there are two tables which retain the DefaultLocationID in the database. During the 1811 upgrade, it changes the DefaultLocationID. What happens to create the behavior that Manish and I were experiencing is the 1811 upgrade fails to update one of the tables. So, the DefaultLocationID information is mismatched and that created this behavior.
The instant the AW support person fixed it so they matched, profile deployments and DEP enrollments worked again. Even the ' Global OG Error' that Manish mentioned above is fixed.
So, long story short, if you get this behavior, I recommend opening an AW ticket and have them check if your DefaultLocationID information is mismatched in the two tables.
Sean