Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About FoozGrind
FoozGrind
Comes here often
Member since Aug 1, 2019
Aug 2 2019
Community Record
6
Posts
0
Kudos
0
Solutions
Badges
Aug 2 2019
6:54 AM
Much appreciated for the info! I am going to send an email off to our networking team with the suggestion 🙂
... View more
Aug 2 2019
5:51 AM
Correct I just joined the company a few months ago and yea we now started naming the networks with the windows username so at least we know who it belongs to from just looking at the organization tab but other than that we have an excel spreadsheet we use in FL to help identity who network 204 would belong to IF it was entered into that spreadsheet. Then we have our other home office in Utah using some other way of tracking who they send them to... We dont have an asset management system until recently so hopefully we can use that to help. But as of now I believe HR asks the user do you have remote equipment user says yes they send us a ticket we send them boxes and hope we get the devices back. IF we dont get the device back and we dont know which VPN network it is technically even though their network account is disabled they can still log into anyone phone extension since the avaya phone ext and password are the same as the extension plus if they wanted to they could connect their own computer to the meraki and surf the internet or try and access or network devices although they wouldn't have a network account so its really how much effort they want to put into that.
... View more
Aug 2 2019
5:36 AM
What about setting up radius authentication by workstation on the vlan coming in from the meraki devices? In the dashboard each network is called "RemoteUser201,202,203,204 etc...) When i go into the network I can see the users name at the top if it was typed in and we have the address etc.... The problem is when the person leaves the company if we dont know then we cannot disable the meraki. Its worse than that if we dont know what the serial number is or what the name of the network is then we play the guessing game...
... View more
Aug 1 2019
1:31 PM
Would you be able to provide some links or guide on how to make this script? Is it running against the dashboard? Would our security team need to handle this? Just trying to figure out how this would work.
... View more
Aug 1 2019
7:47 AM
Hey not sure what that is.... I am little green. What I do now is log into our meraki dashboard. Claim the Serial, create a network for the device assign it the proper template then name the device fill in the user information and then tag it with the proper vlan. Hand it off the user and that is the last I see it.
... View more
Aug 1 2019
6:28 AM
Hi everyone, I hope this question is in the correct forum. At my current company we have about 300 Meraki hardware devices in the field support remote users. We are allowing them to access our phone system with a physical Avaya IP phone and company issued computer. When a user is separated we do not have a really good way of knowing if a user had remote equipment unless HR lets us know. Even than we are not guaranteed to get the equipment returned to us. So at this point even though the network acnt is disabled they could technically still log into anyone's extension with the Avaya phone and plug in any computer of their own and have network access although it wouldn't be a domain computer but they could still obtain an IP and snoop. Is there a way to somehow completely cut access to the device automatically upon a user being terminated or leaving the company? This way if HR forgets to tell us or the user doesn't send the computer back our network is still safe? Thanks!
... View more
© 2024 Cisco Systems, Inc.
