CLEANACCESS Archives

October 2007

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Eric Kenny <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Wed, 3 Oct 2007 10:21:10 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
Jackie,

You are my savior.  Thank you very  much, that worked!

Eric


> Eric,
>
> Let's say for role "student", create 2 WSUS requirements with "Cisco
> Rules",
>
> WSUS_A: goes to MS update servers
> WSUS_B: goes to WSUS servers
>
> And you create a check, say check_A, for the registry, if the check
> success, it means it needs to go to WSUS servers, if it fails, it  
> needs
> to go to MS update servers. So, you will have 2 rules,
>
> Rule_A: Check_A
> Rule_B: !Check_A
>
> Assume the Cisco hotfix rule is "pr_XP_Hotfixes".
>
> Then, you map
>
> WSUS_A: check "any of selected rule succeeds" and check "Rule_A" and
> "pr_XP_Hotfixes"
> WSUS_B: check "any of selected rule succeeds" and check "Rule_B" and
> "pr_XP_Hotfixes"
>
> This way, when it executes, you have 3 cases..
>
> 1. pr_XP_Hotfixes passes... So, you don't hit any of the WSUS
> remediation requirement 2. pr_XP_Hotfixes fails, and Check_A passes
> (Rule_A passes and Rule_B fails), WSUS_A will pass and WSUS_B will  
> fail
> and go into WSUS_B remediation.. Remember if check_A passes, it  
> needs to
> go to WSUS servers.
> 3. pr_XP_Hotfixes fails, and Check_A fails (Rule_A fails and Rule_B
> passes), WSUS_B will pass and WSUS_A will fail go into WSUS_A
> remediation.. Remember if check_A fails, it needs to go to MS Update
> servers.
>
> HTH,
> Thanks,
> --Jackie
>

ATOM RSS1 RSS2