I have a set of data: Domains; Users; Machines
I have a task that requires me to check to see if a domain user has logged into a particular machine in the past.
There are unlimited domains, an undefined number of users, and the machine name could potentially change at any time. The tool has to be able to potentially check hundreds to new user/machine combinations at a time. The reason for separating by domain is because the user/machine reports have to be sent to each domain rep individually.
What I thought I was going to do was create a dictionary of domains, a dictionary of users, and a collection of machines, this way I would be able to use the .exists property instead of looping through collections or arrays which is the current problem with my previous code (time to run the tool).
<tab> [TABLE="width: 200, align: left"]
<tbody>[TR]
[TD]Domain[/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD]User[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD][/TD]
[TD]User[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD]Domain[/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD]User[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
</tbody>[/TABLE]
But I found that when it was time to add a new user to an existing domain, I could not - or I was simply doing it incorrectly.
Currently, the data is set up as such:
[TABLE="class: grid, width: 500"]
<tbody>[TR]
[TD]User[/TD]
[TD]Machine[/TD]
[TD]Domain[/TD]
[/TR]
</tbody>[/TABLE]
I'm not including my code because it's completely non-functional and would only add to confusion, but I'd be happy to include more examples if needed. Any suggestions at making this work?</tab>
I have a task that requires me to check to see if a domain user has logged into a particular machine in the past.
There are unlimited domains, an undefined number of users, and the machine name could potentially change at any time. The tool has to be able to potentially check hundreds to new user/machine combinations at a time. The reason for separating by domain is because the user/machine reports have to be sent to each domain rep individually.
What I thought I was going to do was create a dictionary of domains, a dictionary of users, and a collection of machines, this way I would be able to use the .exists property instead of looping through collections or arrays which is the current problem with my previous code (time to run the tool).
<tab> [TABLE="width: 200, align: left"]
<tbody>[TR]
[TD]Domain[/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD]User[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD][/TD]
[TD]User[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
[TR]
[TD]Domain[/TD]
[TD][/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD]User[/TD]
[TD][/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD]Machine[/TD]
[/TR]
</tbody>[/TABLE]
But I found that when it was time to add a new user to an existing domain, I could not - or I was simply doing it incorrectly.
Currently, the data is set up as such:
[TABLE="class: grid, width: 500"]
<tbody>[TR]
[TD]User[/TD]
[TD]Machine[/TD]
[TD]Domain[/TD]
[/TR]
</tbody>[/TABLE]
I'm not including my code because it's completely non-functional and would only add to confusion, but I'd be happy to include more examples if needed. Any suggestions at making this work?</tab>