How often have you or your users tried to find rooms that are free for your meeting time, your recurring series, that have the capacity and resources you need, and are close to you? Probably enough t...
Updated Feb 27, 2024
Version 2.0
Blog Post
mattwhiting vrod29 It looks like when I try to set the "city" via set-place on a room that was migrated from on-premises to 365 it fails as Matt described before. If I do the same command on a room that was created in 365, it works fine. Also, if I set the city/state/country on the on-premises active directory object it doesn't seem to impact the get-place <identity> | select city, command. City remains blank. I thought that might be a workaround. It looks like when I try to do this same type of thing via the 365 GUI it fails telling me it couldn't write back to the on-premises ad object. I'm assuming that's the real issue because the object still exists on-premises.
How does the city attribute in AD relate to the city attribute on Set-Place?