> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/set-rasdayplan.md).

# Set-RASDayPlan

## SYNOPSIS

Modifies the day plan settings of LogonHours.

## SYNTAX

```powershell
Set-RASDayPlan [-Id] <uint>
 -HourPlan {h00 | h01 | h02 | h03 | h04 | h05 | h06 | h07 | h08 | h09 | h10 | h11 | h12 | h13 | h14 | h15 | h16 | h17 | h18 | h19 | h20 | h21 | h22 | h23}
 -ObjType {LogonHours}
 -WeekDays {None | Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday}
 [-Permission {Deny | Permit}] [<CommonParameters>]
```

```powershell
Set-RASDayPlan [-InputObject] <RASListObj>
 -HourPlan {h00 | h01 | h02 | h03 | h04 | h05 | h06 | h07 | h08 | h09 | h10 | h11 | h12 | h13 | h14 | h15 | h16 | h17 | h18 | h19 | h20 | h21 | h22 | h23}
 -WeekDays {None | Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday}
 [-Permission {Deny | Permit}] [<CommonParameters>]
```

```powershell
Set-RASDayPlan [-Name] <string> [[-SiteId] <uint>]
 -HourPlan {h00 | h01 | h02 | h03 | h04 | h05 | h06 | h07 | h08 | h09 | h10 | h11 | h12 | h13 | h14 | h15 | h16 | h17 | h18 | h19 | h20 | h21 | h22 | h23}
 -ObjType {LogonHours}
 -WeekDays {None | Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday}
 [-Permission {Deny | Permit}] [<CommonParameters>]
```

## DESCRIPTION

Modifies the day plan settings of LogonHours.

## EXAMPLES

### Example 1

```powershell
Set-RASDayPlan -Name LH1 -ObjType LogonHours -WeekDays Saturday -HourPlan h08,h09,h10,h11,h12
```

Modifies the Day Plan Settings of the LogonHours with name LH1 to permit Saturday between 8.00 am and 12.59 pm.

### Example 2

```powershell
Set-RASDayPlan -Id 3 -ObjType LogonHours -WeekDays Sunday,Monday -Permission Deny -HourPlan h12,h13,h14,h15
```

Modifies the Day Plan Settings of the LogonHours with Id 3 to deny Sunday and Monday between 12.00 pm and 3.59 pm.

## PARAMETERS

### -Name

The name of the object to modify the day plan.

```yaml
Type: string
Required: True
Position: 0
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -SiteId

Site ID for which to modify the specified day plan of the object type specified.

If the parameter is omitted, the Site ID of the Licensing Server will be used.

```yaml
Type: uint
Required: False
Position: 1
Default value: 0
Accept pipeline input: False
Accept wildcard characters: False
```

### -Id

The ID of the object to modify the day plan.

```yaml
Type: uint
Required: True
Position: 0
Default value: 0
Accept pipeline input: False
Accept wildcard characters: False
```

### -InputObject

The permitted logon hours property to modify.

To obtain an object of type LogonHours, use the Get-LogonHours cmdlet.

Type reference: [RASListObj](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/raslistobj.md)

```yaml
Type: RASListObj
Required: True
Position: 0
Default value: None
Accept pipeline input: true (ByValue)
Accept wildcard characters: False
```

### -ObjType

The Object Type for which to update the Day Plan settings.

Possible values: LogonHours

Type reference: [DayPlanObjType](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/dayplanobjtype.md)

```yaml
Type: DayPlanObjType
Required: True
Position: Named
Default value: 0
Accept pipeline input: False
Accept wildcard characters: False
```

### -Permission

Permission (Permit/Deny)

Possible values: Deny, Permit

Type reference: [Permission](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/permission.md)

```yaml
Type: Permission
Required: False
Position: Named
Default value: Permit
Accept pipeline input: False
Accept wildcard characters: False
```

### -WeekDays

Week Days

Possible values: None, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday

Type reference: [WeekDays](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/weekdays.md)

```yaml
Type: WeekDays
Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -HourPlan

Hour Plan

Possible values: h00, h01, h02, h03, h04, h05, h06, h07, h08, h09, h10, h11, h12, h13, h14, h15, h16, h17, h18, h19, h20, h21, h22, h23

Type reference: [HourPlan](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/hourplan.md)

```yaml
Type: HourPlan
Required: True
Position: Named
Default value: 0
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### [RASListObj](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/types/raslistobj.md)

## OUTPUTS

### None

## RELATED LINKS

* [Get-RASDayPlan](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/get-rasdayplan.md)
* [Set-RASLogonHours](https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/set-raslogonhours.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-powershell-api-guide/rasadmin/cmdlets/set-rasdayplan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
